CVE-2024-10967

7.3 HIGH

📋 TL;DR

This critical SQL injection vulnerability in E-Health Care System 1.0 allows remote attackers to execute arbitrary SQL commands by manipulating the 'id' parameter in the delete_user_appointment_request.php file. This could lead to unauthorized data access, modification, or deletion. All users running the vulnerable version are affected.

💻 Affected Systems

Products:
  • code-projects E-Health Care System
Versions: 1.0
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: Affects the web interface component accessible via HTTP/HTTPS.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise including patient health records, appointment data, user credentials, and potential system takeover via SQL injection leading to remote code execution.

🟠

Likely Case

Unauthorized access to sensitive patient data, appointment manipulation, and potential data exfiltration or destruction.

🟢

If Mitigated

Limited impact with proper input validation and database permissions, potentially only affecting non-sensitive data.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploit details are publicly available on GitHub, making this easily exploitable by attackers with basic SQL injection knowledge.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

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

Restart Required: No

Instructions:

1. Check vendor website for updates 2. Apply any available patches 3. Test functionality after patching

🔧 Temporary Workarounds

Input Validation Filter

all

Add server-side validation to ensure 'id' parameter contains only numeric values

Modify /Doctor/delete_user_appointment_request.php to validate $_GET['id'] or $_POST['id'] is numeric

WAF Rule

all

Implement web application firewall rules to block SQL injection patterns

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

🧯 If You Can't Patch

  • Implement strict input validation and parameterized queries in the affected PHP file
  • Restrict database user permissions to minimum required and implement network segmentation

🔍 How to Verify

Check if Vulnerable:

Test the /Doctor/delete_user_appointment_request.php endpoint with SQL injection payloads in the 'id' parameter

Check Version:

Check system documentation or configuration files for version information

Verify Fix Applied:

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

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL error messages in web server logs
  • Multiple failed delete requests with malformed parameters
  • Requests to delete_user_appointment_request.php with non-numeric ID values

Network Indicators:

  • HTTP requests with SQL keywords in URL parameters
  • Unusual database query patterns from web server

SIEM Query:

source="web_server.log" AND ("delete_user_appointment_request.php" AND ("UNION" OR "SELECT" OR "INSERT" OR "DELETE" OR "DROP"))

🔗 References

📤 Share & Export