Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') (CWE-89)
A critical vulnerability has been discovered in code-projects Restaurant Reservation System version 1.0. The vulnerability affects an unknown function in the /filter.php file. By manipulating the 'from' and 'to' arguments, an attacker can perform SQL injection. This vulnerability can be exploited remotely, and public exploit code is available.
This SQL injection vulnerability could allow an attacker to execute arbitrary SQL commands on the underlying database. Given the CVSS v3.1 score of 9.8 (Critical), the potential impacts are severe: 1. Data Breach: Attackers could potentially access, modify, or delete sensitive information stored in the database, including customer details and reservation data. 2. System Compromise: Depending on the database configuration, attackers might be able to execute operating system commands, potentially leading to full system compromise. 3. Data Integrity: Unauthorized modifications to the database could result in incorrect reservations, financial discrepancies, or other operational issues. 4. Service Disruption: Malicious SQL queries could overload the database, causing denial of service and disrupting the reservation system's functionality. The vulnerability is particularly concerning due to its network attack vector, low attack complexity, and the fact that it requires no privileges or user interaction to exploit.
One proof-of-concept exploit is available on github.com. There is no evidence of proof of exploitation at the moment.
As of the latest information provided, there is no mention of an available patch for this vulnerability in Restaurant Reservation System 1.0. Users of this software should contact code-projects for update information and mitigation strategies.
Until a patch is available, consider the following mitigation strategies: 1. Input Validation: Implement strict input validation for the 'from' and 'to' parameters in the /filter.php file. 2. Parameterized Queries: Use parameterized SQL queries or prepared statements to prevent SQL injection. 3. Least Privilege: Ensure the database user account used by the application has minimal necessary privileges. 4. Web Application Firewall (WAF): Deploy a WAF to help filter out malicious requests. 5. Network Segmentation: If possible, place the database server in a separate network segment with restricted access. 6. Monitoring: Implement robust logging and monitoring to detect potential exploitation attempts. 7. Consider Temporary Workaround: If feasible, temporarily disable or restrict access to the /filter.php file until a proper fix is in place.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Feedly found the first article mentioning CVE-2024-9086. See article
Feedly estimated the CVSS score as HIGH
NVD published the first details for CVE-2024-9086
A CVSS base score of 6.3 has been assigned.
EPSS Score was set to: 0.05% (Percentile: 16.3%)
A CVSS base score of 9.8 has been assigned.
A CVSS base score of 9.8 has been assigned.