CVE-2024-10791

7.3 HIGH

📋 TL;DR

A critical SQL injection vulnerability exists in Codezips Hospital Appointment System 1.0 through the /doctorAction.php file's Name parameter. This allows remote attackers to execute arbitrary SQL commands on the database. All deployments of version 1.0 are affected.

💻 Affected Systems

Products:
  • Codezips Hospital Appointment System
Versions: 1.0
Operating Systems: Any
Default Config Vulnerable: ⚠️ Yes
Notes: All installations of version 1.0 are vulnerable. The researcher advisory mentions conflicting file/parameter names, suggesting possible variations in exploitation.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise leading to data theft, data manipulation, authentication bypass, and potential remote code execution via database functions.

🟠

Likely Case

Unauthorized access to sensitive patient and appointment data, including personal health information and medical records.

🟢

If Mitigated

Limited impact with proper input validation and parameterized queries preventing successful exploitation.

🌐 Internet-Facing: HIGH - The vulnerability is remotely exploitable and public exploit details exist.
🏢 Internal Only: MEDIUM - Internal attackers could exploit this, but external threat is higher.

🎯 Exploit Status

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

Exploit details are publicly available on GitHub. SQL injection vulnerabilities are commonly weaponized in automated attacks.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: None found

Restart Required: No

Instructions:

No official patch available. Consider implementing workarounds or migrating to a different system.

🔧 Temporary Workarounds

Input Validation Filter

all

Add server-side validation to reject malicious input in the Name parameter

Modify /doctorAction.php to sanitize the Name parameter using prepared statements or strict input validation

Web Application Firewall

all

Deploy WAF rules to block SQL injection patterns

Add WAF rule: deny requests containing SQL keywords like UNION, SELECT, INSERT, DELETE in Name parameter

🧯 If You Can't Patch

  • Isolate the system behind a firewall with strict access controls
  • Implement network segmentation to limit database access from the web server

🔍 How to Verify

Check if Vulnerable:

Test the /doctorAction.php endpoint with SQL injection payloads in the Name parameter (e.g., Name=test' OR '1'='1)

Check Version:

Check system documentation or configuration files for version information

Verify Fix Applied:

Verify that SQL injection payloads no longer produce database errors or unexpected results

📡 Detection & Monitoring

Log Indicators:

  • Unusual database queries from web server
  • SQL syntax errors in application logs
  • Multiple failed login attempts via /doctorAction.php

Network Indicators:

  • HTTP requests to /doctorAction.php with SQL keywords in parameters
  • Unusual database traffic patterns

SIEM Query:

source="web_logs" AND uri="/doctorAction.php" AND (param="*UNION*" OR param="*SELECT*" OR param="*INSERT*")

🔗 References

📤 Share & Export