CVE-2024-10409

6.3 MEDIUM

📋 TL;DR

This critical SQL injection vulnerability in Blood Bank Management 1.0 allows remote attackers to execute arbitrary SQL commands via the reqid parameter in /file/accept.php. Attackers can potentially read, modify, or delete database content, including sensitive blood bank records. All users running the affected software are at risk.

💻 Affected Systems

Products:
  • Blood Bank Management
Versions: 1.0
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: Affects the specific file /file/accept.php when handling reqid parameter. No authentication required for exploitation.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise leading to data theft, data destruction, or full system takeover via SQL injection to RCE chaining.

🟠

Likely Case

Unauthorized access to sensitive blood donor and patient data, including personal information and medical records.

🟢

If Mitigated

Limited impact with proper input validation and database permissions restricting damage to non-critical data.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Public exploit available via GitHub gist. Simple SQL injection requiring minimal technical skill.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: https://code-projects.org/

Restart Required: No

Instructions:

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

🔧 Temporary Workarounds

Input Validation Filter

all

Add server-side validation to sanitize reqid parameter before processing

Modify /file/accept.php to validate reqid as integer using is_numeric() or similar

WAF Rule

all

Block SQL injection patterns targeting /file/accept.php

Add WAF rule: deny requests to /file/accept.php containing SQL keywords in reqid parameter

🧯 If You Can't Patch

  • Isolate the system behind a firewall with strict access controls
  • Implement database-level protections: use least privilege accounts, enable audit logging

🔍 How to Verify

Check if Vulnerable:

Test /file/accept.php with SQL injection payloads in reqid parameter (e.g., reqid=1' OR '1'='1)

Check Version:

Check software version in admin panel or configuration files

Verify Fix Applied:

Verify that SQL injection attempts return error messages or are blocked

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL errors in application logs
  • Multiple requests to /file/accept.php with suspicious parameters

Network Indicators:

  • HTTP requests to /file/accept.php containing SQL keywords (UNION, SELECT, etc.)

SIEM Query:

source="web_logs" AND uri="/file/accept.php" AND (reqid="*'*" OR reqid="*UNION*" OR reqid="*SELECT*")

🔗 References

📤 Share & Export