CVE-2024-10997

6.3 MEDIUM

📋 TL;DR

This critical SQL injection vulnerability in 1000 Projects Bookstore Management System 1.0 allows remote attackers to execute arbitrary SQL commands via the 'id' parameter in /book_list.php. Attackers can potentially read, modify, or delete database content, including sensitive information like user credentials and transaction records. All deployments of version 1.0 are affected.

💻 Affected Systems

Products:
  • 1000 Projects Bookstore Management System
Versions: 1.0
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: All installations of version 1.0 are vulnerable by default. The vulnerability exists in core functionality.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise leading to data theft, data destruction, authentication bypass, and potential server takeover via SQL injection to RCE chaining.

🟠

Likely Case

Unauthorized data access and extraction of sensitive information including user credentials, personal data, and financial records.

🟢

If Mitigated

Limited impact with proper input validation and WAF rules blocking SQL injection patterns.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Public exploit code is available on GitHub. The vulnerability requires no authentication and has simple exploitation vectors.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: None available

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 'id' parameter in book_list.php

Modify book_list.php to use prepared statements: $stmt = $conn->prepare('SELECT * FROM books WHERE id = ?'); $stmt->bind_param('i', $_GET['id']);

Web Application Firewall Rules

all

Deploy WAF rules to block SQL injection patterns targeting /book_list.php

ModSecurity rule: SecRule ARGS:id "@detectSQLi" "id:1001,phase:2,deny,status:403,msg:'SQLi attempt detected'"

🧯 If You Can't Patch

  • Network segmentation: Isolate the vulnerable system from sensitive networks and databases
  • Access controls: Restrict access to /book_list.php via authentication or IP whitelisting

🔍 How to Verify

Check if Vulnerable:

Test /book_list.php?id=1' OR '1'='1 and observe if SQL errors or unexpected results appear

Check Version:

Check system documentation or about page for version information

Verify Fix Applied:

Test with SQL injection payloads and verify they are blocked or sanitized

📡 Detection & Monitoring

Log Indicators:

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

Network Indicators:

  • HTTP requests to /book_list.php with SQL keywords in parameters
  • Unusual database traffic patterns from web server

SIEM Query:

source="web_logs" AND uri_path="/book_list.php" AND (param_id CONTAINS "'" OR param_id CONTAINS "OR" OR param_id CONTAINS "UNION")

🔗 References

📤 Share & Export