CVE-2017-17606

9.8 CRITICAL

📋 TL;DR

CVE-2017-17606 is a critical SQL injection vulnerability in Co-work Space Search Script 1.0 that allows attackers to execute arbitrary SQL commands via the /list city parameter. This affects all installations of version 1.0 of this software. Successful exploitation could lead to complete database compromise.

💻 Affected Systems

Products:
  • Co-work Space Search Script
Versions: 1.0
Operating Systems: All platforms running PHP/MySQL
Default Config Vulnerable: ⚠️ Yes
Notes: Affects all installations of version 1.0 regardless of configuration.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise including data theft, data manipulation, authentication bypass, and potential remote code execution if database functions allow it.

🟠

Likely Case

Database information disclosure, data manipulation, and potential privilege escalation.

🟢

If Mitigated

Limited impact with proper input validation and parameterized queries in place.

🌐 Internet-Facing: HIGH - The vulnerability is in a web application parameter that is typically internet-accessible.
🏢 Internal Only: MEDIUM - Internal systems could still be vulnerable if accessed by malicious insiders or compromised accounts.

🎯 Exploit Status

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

Public exploit code is available and exploitation requires no authentication.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown - No official patch released

Vendor Advisory: No official vendor advisory found

Restart Required: No

Instructions:

No official patch available. Consider migrating to alternative software or implementing workarounds.

🔧 Temporary Workarounds

Input Validation and Sanitization

all

Implement strict input validation and parameterized queries for the city parameter

Modify PHP code to use prepared statements: $stmt = $pdo->prepare('SELECT * FROM table WHERE city = ?'); $stmt->execute([$city]);

WAF Rule Implementation

all

Deploy web application firewall rules to block SQL injection attempts

Add WAF rule: SecRule ARGS:city "@detectSQLi" "id:1001,phase:2,deny,status:403,msg:'SQL Injection Attempt'"

🧯 If You Can't Patch

  • Isolate the vulnerable system behind a reverse proxy with strict input filtering
  • Implement network segmentation to limit database access from the vulnerable application

🔍 How to Verify

Check if Vulnerable:

Test the /list endpoint with SQL injection payloads like: /list?city=test' OR '1'='1

Check Version:

Check script version in source code or documentation files

Verify Fix Applied:

Test with same payloads and verify they are rejected or properly sanitized

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL error messages in application logs
  • Multiple failed parameter validation attempts
  • Suspicious city parameter values containing SQL keywords

Network Indicators:

  • HTTP requests with SQL injection patterns in city parameter
  • Unusual database query patterns from application server

SIEM Query:

source="web_logs" AND uri_path="/list" AND (city="*' OR*" OR city="*UNION*" OR city="*SELECT*" OR city="*--*" OR city="*;*" OR city="*/*")

🔗 References

📤 Share & Export