CVE-2024-6905

6.3 MEDIUM

📋 TL;DR

This critical SQL injection vulnerability in SourceCodester Record Management System 1.0 allows attackers to manipulate database queries through the 'id' parameter in view_info_user.php. Remote attackers can potentially access, modify, or delete sensitive database records. All deployments of this specific software version are affected.

💻 Affected Systems

Products:
  • SourceCodester Record Management System
Versions: 1.0
Operating Systems: Any
Default Config Vulnerable: ⚠️ Yes
Notes: Affects all installations of version 1.0 regardless of configuration.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise including data theft, data destruction, or full system takeover via SQL injection leading to remote code execution.

🟠

Likely Case

Unauthorized access to sensitive user records, personal information exposure, and potential privilege escalation.

🟢

If Mitigated

Limited impact with proper input validation and database permissions restricting query execution.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Public exploit available on GitHub, simple parameter manipulation required.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: None available

Restart Required: No

Instructions:

No official patch available. Consider replacing with alternative software or implementing workarounds.

🔧 Temporary Workarounds

Input Validation Filter

all

Add server-side validation to sanitize the 'id' parameter before processing

Modify view_info_user.php to validate/sanitize the id parameter using prepared statements or parameterized queries

WAF Rule Implementation

all

Deploy 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

  • Isolate the system behind a reverse proxy with strict input validation
  • Implement network segmentation to limit database access from the vulnerable application

🔍 How to Verify

Check if Vulnerable:

Test the view_info_user.php endpoint with SQL injection payloads in the 'id' parameter

Check Version:

Check application version in admin panel or configuration files

Verify Fix Applied:

Verify that SQL injection attempts no longer succeed and return proper error handling

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL error messages in application logs
  • Multiple rapid requests to view_info_user.php with varying id parameters

Network Indicators:

  • HTTP requests containing SQL keywords in URL parameters
  • Unusual database query patterns from application server

SIEM Query:

source="web_logs" AND (url="*view_info_user.php*" AND (param="*id=*UNION*" OR param="*id=*SELECT*" OR param="*id=*OR*"))

🔗 References

📤 Share & Export