CVE-2017-15964

9.8 CRITICAL

📋 TL;DR

This vulnerability allows attackers to execute arbitrary SQL commands through the PATH_INFO parameter in /job-details URLs in Job Board Script Software. This affects all users running vulnerable versions of the software, potentially exposing database contents including user credentials and job postings.

💻 Affected Systems

Products:
  • Job Board Script Software
Versions: 1.0
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: Affects web applications using the vulnerable script, typically PHP-based installations.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise leading to data theft, authentication bypass, remote code execution via database functions, and full system takeover.

🟠

Likely Case

Unauthorized access to sensitive job application data, user information theft, and potential privilege escalation.

🟢

If Mitigated

Limited impact with proper input validation and parameterized queries preventing SQL injection.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Multiple public exploit scripts available requiring minimal technical skill to execute.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: Not available

Restart Required: No

Instructions:

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

🔧 Temporary Workarounds

Input Validation Filter

all

Implement strict input validation for PATH_INFO parameter in /job-details endpoints

Modify PHP code to sanitize $_SERVER['PATH_INFO'] using preg_replace('/[^a-zA-Z0-9\-\_]/', '', $input)

WAF Rule Implementation

all

Deploy web application firewall rules to block SQL injection patterns in URL paths

Add WAF rule: SecRule REQUEST_URI "@rx (?i)(union|select|insert|update|delete|drop|create|alter).*" "id:1001,phase:2,deny"

🧯 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 web servers

🔍 How to Verify

Check if Vulnerable:

Test with payload: /job-details/1' OR '1'='1 and observe database errors or unexpected behavior

Check Version:

Check software version in admin panel or readme files

Verify Fix Applied:

Attempt SQL injection payloads and verify they are rejected or sanitized without database errors

📡 Detection & Monitoring

Log Indicators:

  • SQL syntax errors in web server logs
  • Unusual database query patterns from web application
  • Multiple failed parameter parsing attempts

Network Indicators:

  • HTTP requests with SQL keywords in URL paths
  • Abnormal database connection patterns from web servers

SIEM Query:

source="web_logs" AND (url="*job-details*" AND (url="*union*" OR url="*select*" OR url="*' OR '*"))

🔗 References

📤 Share & Export