CVE-2024-24495

9.8 CRITICAL

📋 TL;DR

This SQL injection vulnerability in Daily Habit Tracker v1.0 allows remote attackers to execute arbitrary SQL commands via crafted GET requests to delete-tracker.php. Attackers can potentially read, modify, or delete database contents, and in some configurations execute arbitrary code. All users running the vulnerable version are affected.

💻 Affected Systems

Products:
  • Daily Habit Tracker
Versions: v1.0
Operating Systems: Any OS running PHP
Default Config Vulnerable: ⚠️ Yes
Notes: Requires PHP environment with database connectivity. Default installation is vulnerable.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete system compromise via SQL injection leading to remote code execution, database destruction, and unauthorized access to sensitive user data.

🟠

Likely Case

Database manipulation including reading/modifying/deleting habit tracking data, user credentials, and potentially gaining administrative access.

🟢

If Mitigated

Limited impact with proper input validation and database permissions, potentially only allowing data viewing without modification.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploit requires simple HTTP GET requests with SQL injection payloads. Public proof-of-concept available in GitHub repository.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: None available

Restart Required: No

Instructions:

No official patch available. Consider implementing parameterized queries and input validation as workaround.

🔧 Temporary Workarounds

Implement Parameterized Queries

all

Replace vulnerable SQL queries with prepared statements using parameterized queries.

Input Validation and Sanitization

all

Add strict input validation for all GET parameters in delete-tracker.php.

🧯 If You Can't Patch

  • Implement web application firewall (WAF) with SQL injection rules
  • Restrict access to delete-tracker.php via network controls or authentication

🔍 How to Verify

Check if Vulnerable:

Test delete-tracker.php with SQL injection payloads like ' OR '1'='1 in GET parameters

Check Version:

Check PHP files for version information or consult installation documentation

Verify Fix Applied:

Verify parameterized queries are implemented and test with SQL injection payloads

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL errors in application logs
  • Multiple failed delete operations
  • Requests with SQL keywords in parameters

Network Indicators:

  • HTTP GET requests to delete-tracker.php with SQL injection patterns
  • Unusual database query patterns

SIEM Query:

source="web_logs" AND uri="*delete-tracker.php*" AND (param="*OR*" OR param="*UNION*" OR param="*SELECT*" OR param="*INSERT*")

🔗 References

📤 Share & Export