You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A SQL injection vulnerability was identified in the 'login.php' file of the 'Online Blood Bank Management System' project developed in PHP. The root cause of this issue is that malicious code can be injected through the "user" parameter, which is then directly used in SQL queries without proper sanitization or validation. This flaw permits attackers to manipulate input values, consequently altering SQL queries and executing unauthorized operations.
Impact
Attackers can exploit this SQL injection vulnerability to achieve unauthorized database access, sensitive data leakage, data tampering, comprehensive system control, and even service interruption, posing a serious threat to system security and business continuity.
DESCRIPTION
Due to insufficient user input validation for the "user" parameter, a serious SQL injection vulnerability was discovered in the login function of the "Online Blood Bank Management System" in PHP", allowing attackers to inject malicious SQL queries. Therefore, attackers can gain unauthorized access to the database, modify or delete data, and access sensitive information without logging in. Immediate remedial measures are needed to ensure system security and protect data integrity.
Parameter: user (POST)
Type: time-based blind
Title: MySQL >= 5.0.12 AND time-based blind (query SLEEP)
Payload: tab=on&user=123321' AND (SELECT 8755 FROM (SELECT(SLEEP(5)))xGkg) AND 'emTj'='emTj&pass=123123&sub=Log In
The following are screenshots of some specific information obtained from testing and running with the sqlmap tool:
sqlmap -r 123 --batch --dbs
Suggested repair
Use prepared statements and parameter binding:
Utilizing prepared statements can effectively prevent SQL injection by isolating SQL code from user input. This ensures that user-provided values are handled strictly as data, not executable SQL commands.
Input validation and filtering:
Enforce strict validation and filtering of user input to guarantee it adheres to the expected format and standards.
Minimize database user permissions:
Configure database accounts to have only the necessary permissions needed for their tasks. Refrain from using highly privileged accounts (like 'root' or 'admin') for routine operations.
Regular security audits:
Conduct frequent code and system security audits to quickly identify and rectify any potential security vulnerabilities.
Citation: Follow same issue format from ppp-src/ha#3
The text was updated successfully, but these errors were encountered:
Itsourcecode "Online Blood Bank Management System" in PHP 1.0 "login.php" SQL injection
NAME OF AFFECTED PRODUCT(S)
Vendor Homepage
AFFECTED AND/OR FIXED VERSION(S)
submitter
Vulnerable File
VERSION(S)
Software Link
PROBLEM TYPE
Vulnerability Type
Root Cause
Impact
DESCRIPTION
Vulnerability details and POC
Vulnerability type:
Vulnerability location:
Payload:
The following are screenshots of some specific information obtained from testing and running with the sqlmap tool:
Suggested repair
Use prepared statements and parameter binding:
Utilizing prepared statements can effectively prevent SQL injection by isolating SQL code from user input. This ensures that user-provided values are handled strictly as data, not executable SQL commands.
Input validation and filtering:
Enforce strict validation and filtering of user input to guarantee it adheres to the expected format and standards.
Minimize database user permissions:
Configure database accounts to have only the necessary permissions needed for their tasks. Refrain from using highly privileged accounts (like 'root' or 'admin') for routine operations.
Regular security audits:
Conduct frequent code and system security audits to quickly identify and rectify any potential security vulnerabilities.
Citation: Follow same issue format from ppp-src/ha#3
The text was updated successfully, but these errors were encountered: