Executive Summary

This vulnerability is a critical SQL injection flaw in the Digital Crime Report Management System 1.0 that affects multiple login pages. Attackers can send specially crafted SQL injection payloads in the email and password fields of police, incharge, user, and HQ login endpoints. This allows them to manipulate the SQL queries used for authentication, bypassing login checks without valid credentials and gaining unauthorized access to the system. [2, 4]

Useful 0 Not Useful 0

Impact Analysis

The vulnerability allows unauthenticated attackers to bypass authentication and gain unauthorized access to the Digital Crime Report Management System. This can lead to exposure of sensitive data, unauthorized actions within the system, and potential compromise of the integrity of crime report management processes. Since attackers do not need any privileges or user interaction to exploit this, it poses a high security risk. [2, 4]

Useful 0 Not Useful 0

Detection Guidance

This vulnerability can be detected by testing the login endpoints (policelogin.php, inchargelogin.php, userlogin.php, headlogin.php) for SQL injection by sending crafted SQL payloads in the 'email' and 'password' POST parameters. For example, you can use curl commands to send payloads like: curl -X POST -d "email='or''='&password='or''='&s=" http://targetsite/policelogin.php and observe if authentication is bypassed. Detection involves checking if the system allows login without valid credentials by manipulating SQL queries through these parameters. [4]

Useful 0 Not Useful 0

Mitigation Strategies

Immediate mitigation steps include implementing proper input validation and sanitization on all login endpoints, using prepared statements or parameterized queries to prevent SQL injection, and restricting access to these endpoints if possible. Additionally, monitoring and blocking suspicious requests containing SQL injection payloads can help reduce exploitation risk until a patch or update is applied. [4, 2]

Useful 0 Not Useful 0