CVE-2017-17627

9.8 CRITICAL

📋 TL;DR

This vulnerability allows attackers to execute arbitrary SQL commands via the report_videos parameter in single-video-detail.php in Readymade Video Sharing Script 3.2. This can lead to data theft, modification, or deletion. Anyone using this specific version of the script is affected.

💻 Affected Systems

Products:
  • Readymade Video Sharing Script
Versions: Version 3.2
Operating Systems: All platforms running PHP
Default Config Vulnerable: ⚠️ Yes
Notes: Affects all installations of version 3.2 regardless of configuration.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise allowing data exfiltration, modification, or deletion, and potential remote code execution if database permissions allow.

🟠

Likely Case

Unauthorized access to sensitive user data, video metadata, and administrative credentials stored in the database.

🟢

If Mitigated

Limited impact with proper input validation and database permission restrictions in place.

🌐 Internet-Facing: HIGH - The vulnerable script is typically internet-facing in video sharing applications.
🏢 Internal Only: LOW - This is a web application vulnerability primarily affecting internet-facing systems.

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: CONFIRMED
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Public exploit code is available and exploitation requires minimal technical skill.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: No official vendor advisory found

Restart Required: No

Instructions:

1. Upgrade to a newer version if available. 2. If no upgrade exists, manually patch the single-video-detail.php file to implement proper input validation and parameterized queries.

🔧 Temporary Workarounds

Input Validation Filter

all

Add input validation to sanitize the report_videos parameter

Edit single-video-detail.php and add: $report_videos = intval($_POST['report_videos']);

WAF Rule

all

Implement web application firewall rules to block SQL injection patterns

Add WAF rule: Detect and block SQL injection patterns in POST parameters

🧯 If You Can't Patch

  • Implement network segmentation to isolate the vulnerable system
  • Deploy a web application firewall with SQL injection detection rules

🔍 How to Verify

Check if Vulnerable:

Test the single-video-detail.php endpoint with SQL injection payloads in the report_videos parameter

Check Version:

Check script version in admin panel or configuration files

Verify Fix Applied:

Verify that SQL injection payloads no longer execute and return error messages

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL error messages in application logs
  • Multiple failed login attempts from single IP
  • Unexpected database queries

Network Indicators:

  • SQL keywords in POST parameters to single-video-detail.php
  • Unusual database connection patterns

SIEM Query:

source="web_logs" AND (uri="*single-video-detail.php*" AND (param="*report_videos*" AND value="*UNION*" OR value="*SELECT*" OR value="*INSERT*" OR value="*DELETE*"))

🔗 References

📤 Share & Export