CVE-2024-0357 Overview
A critical SQL injection vulnerability has been discovered in coderd-repos Eva version 1.0.0. This vulnerability affects the HTTP POST Request Handler component, specifically within the /system/traceLog/page endpoint. Manipulation of the argument property allows attackers to inject arbitrary SQL commands, potentially leading to unauthorized data access, modification, or deletion.
Critical Impact
This SQL injection vulnerability allows unauthenticated remote attackers to execute arbitrary SQL commands against the backend database, potentially compromising all stored data and enabling complete system takeover.
Affected Products
- coderd-repos Eva 1.0.0
Discovery Timeline
- 2024-01-10 - CVE-2024-0357 published to NVD
- 2024-11-21 - Last updated in NVD database
Technical Details for CVE-2024-0357
Vulnerability Analysis
This vulnerability exists in the trace log pagination functionality of coderd-repos Eva. The application fails to properly sanitize user-supplied input in the property argument when processing HTTP POST requests to the /system/traceLog/page endpoint. This lack of input validation allows attackers to inject malicious SQL statements that are directly concatenated into database queries without proper parameterization or escaping.
The vulnerability is particularly severe because it requires no authentication and can be exploited remotely over the network. An attacker can leverage this flaw to extract sensitive information from the database, modify or delete data, and potentially gain further access to the underlying system depending on database privileges.
Root Cause
The root cause of CVE-2024-0357 is insufficient input validation and the absence of parameterized queries in the HTTP POST Request Handler. The property argument is directly incorporated into SQL statements without proper sanitization, allowing specially crafted input to modify the structure and behavior of database queries. This represents a classic CWE-89 (Improper Neutralization of Special Elements used in an SQL Command) vulnerability pattern.
Attack Vector
The attack can be executed remotely over the network by sending a malicious HTTP POST request to the /system/traceLog/page endpoint. The attacker manipulates the property parameter to inject SQL commands that are executed by the database server. No authentication is required, and no user interaction is needed to exploit this vulnerability.
The exploitation methodology involves crafting POST requests with SQL injection payloads in the property parameter. Techniques such as UNION-based injection, boolean-based blind injection, or time-based blind injection may be used depending on the application's response behavior. For detailed technical information, see the GitHub SQL Vulnerability Documentation.
Detection Methods for CVE-2024-0357
Indicators of Compromise
- Unusual or malformed HTTP POST requests to /system/traceLog/page containing SQL syntax or special characters in the property parameter
- Database error messages in application logs indicating SQL syntax errors or unexpected query behavior
- Abnormal database query patterns showing UNION SELECT statements, time delays (SLEEP/WAITFOR), or attempts to access system tables
- Increased database resource utilization or unexpected data access patterns in database audit logs
Detection Strategies
- Deploy Web Application Firewall (WAF) rules to detect and block SQL injection patterns in HTTP POST requests targeting the /system/traceLog/page endpoint
- Implement application-level logging for all requests to the affected endpoint with alerting on suspicious parameter values
- Enable database audit logging to track unusual query patterns, especially those accessing sensitive tables or using injection-related SQL functions
- Use intrusion detection systems (IDS) with signatures for SQL injection attack patterns
Monitoring Recommendations
- Monitor HTTP POST traffic to /system/traceLog/page for requests containing SQL keywords such as SELECT, UNION, INSERT, UPDATE, DELETE, or DROP
- Configure database activity monitoring to alert on queries with unusual structure or attempting to access schema metadata
- Review application and web server logs regularly for patterns consistent with SQL injection reconnaissance or exploitation attempts
How to Mitigate CVE-2024-0357
Immediate Actions Required
- Restrict network access to the affected /system/traceLog/page endpoint using firewall rules or access control lists until a patch is available
- Deploy a Web Application Firewall (WAF) with SQL injection detection rules in front of the affected application
- Implement input validation at the application perimeter to reject requests with suspicious SQL-related characters or patterns
- Review database user privileges and ensure the application uses least-privilege database accounts
Patch Information
At the time of publication, no official vendor patch has been released for this vulnerability. Organizations should monitor the coderd-repos Eva project for security updates. In the absence of an official fix, implement the workarounds and mitigations described below to reduce exposure risk.
For the latest information, refer to VulDB #250124 and the vendor's official channels.
Workarounds
- Implement parameterized queries or prepared statements in the affected code to prevent SQL injection attacks
- Add server-side input validation to sanitize the property parameter, rejecting or escaping special characters used in SQL injection
- Restrict access to the /system/traceLog/page endpoint to authenticated and authorized users only
- Place the application behind a reverse proxy with SQL injection filtering capabilities
# Example WAF rule to block SQL injection attempts (ModSecurity format)
SecRule ARGS:property "@detectSQLi" \
"id:1001,\
phase:2,\
deny,\
status:403,\
msg:'SQL Injection attempt detected in property parameter',\
log,\
auditlog"
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.


