CVE-2024-37802

8.8 HIGH

📋 TL;DR

CVE-2024-37802 is a SQL injection vulnerability in the Health Care Hospital Management System v1.0 that allows attackers to execute arbitrary SQL commands via the searvalu parameter in the Patient Info module. This affects all users running the vulnerable version of this PHP-based hospital management software. Successful exploitation could lead to unauthorized data access, modification, or deletion.

💻 Affected Systems

Products:
  • CodeProjects Health Care Hospital Management System
Versions: v1.0
Operating Systems: Any OS running PHP and MySQL
Default Config Vulnerable: ⚠️ Yes
Notes: Affects all installations of v1.0 regardless of configuration. The software is built with PHP, CSS, JS, and MySQL.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise including patient medical records, financial data, and administrative credentials, potentially leading to data theft, system takeover, or ransomware deployment.

🟠

Likely Case

Unauthorized access to patient information, modification of medical records, or extraction of sensitive data from the database.

🟢

If Mitigated

Limited impact with proper input validation and parameterized queries preventing SQL injection, though other vulnerabilities might still exist.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

SQL injection via GET/POST parameter requires minimal technical skill. Public proof-of-concept exists in GitHub repositories.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: None available

Restart Required: No

Instructions:

No official patch available. Consider upgrading to a newer version if available, or implement parameterized queries and input validation in the Patient Info module.

🔧 Temporary Workarounds

Web Application Firewall (WAF)

all

Deploy a WAF with SQL injection protection rules to block malicious requests.

Input Validation

all

Implement strict input validation for the searvalu parameter to only allow expected characters.

🧯 If You Can't Patch

  • Implement network segmentation to isolate the vulnerable system from critical infrastructure.
  • Disable or restrict access to the Patient Info module if not essential for operations.

🔍 How to Verify

Check if Vulnerable:

Test the searvalu parameter with SQL injection payloads like ' OR '1'='1 in the Patient Info module.

Check Version:

Check the software version in the admin panel or configuration files, typically in index.php or config.php.

Verify Fix Applied:

Verify that SQL injection payloads no longer execute and return error messages or are properly sanitized.

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL queries in application logs
  • Multiple failed login attempts or parameter manipulation in access logs

Network Indicators:

  • HTTP requests containing SQL keywords (SELECT, UNION, etc.) in the searvalu parameter

SIEM Query:

source="web_logs" AND (searvalu="*' OR*" OR searvalu="*UNION*" OR searvalu="*SELECT*" OR searvalu="*--*" OR searvalu="*;*" OR searvalu="*/*")

🔗 References

📤 Share & Export