CVE-2024-8465

CRITICAL

SQL injection vulnerability in Job Portal

Title source: CVE List
Search associated code STIX 2.1 vulnerability STIX 2.1 with PoCs

Record summary

CVE-2024-8465 has a selected CVSS score of 9.8 (critical); EIP currently links 1 repository PoC and 1 lab environment.

Description

SQL injection vulnerability, by which an attacker could send a specially designed query through user_id parameter in /jobportal/admin/user/controller.php, and retrieve all the information stored in it.

Description source: CVE List

Exploitation context

Available material

Repository PoCs
1
Lab environments
1

CISA SSVC decision

ExploitationNone
AutomatableNo
Technical impactTotal

CISA Coordinator · SSVC 2.0.3 · Evaluated Sep 5, 2024 · Source: CVE List

Affected products and versions

1
ProductSourceVersion range

Job Portal

Browse PHPGurukul / Job Portal

Default status: unaffected, unknown

CVE List1.0affected

Proofs of concept

1

Repository PoCs

GitHub19melek19/TheMisfits-CVE-2024-8465-SQLiRepository PoCby 19melek190Writeup17 files

13.3 KiB

GitHub
PoC details
Analysisdeepseek-v4-pro:cloud ·

Technical assessment

The artifact is a README and Dockerfile for an intentionally vulnerable web application created to demonstrate SQL injection techniques inspired by CVE-2024-8465. It describes vulnerable endpoints, example payloads, and setup instructions, but contains no exploit or scanner code.

Backdoor review

No backdoor observed in reviewed code

The reviewed evidence consists of a README.md and a Dockerfile for a deliberately vulnerable web application PoC for CVE-2024-8465. The README describes SQL injection vulnerabilities and setup instructions. The Dockerfile installs the mysqli extension. No backdoor, deceptive payload, or concealed harmful behavior is present in the supplied text.

ClassificationWriteup
Model confidence95%
AuthenticationNot required
LanguagesEnglish
Target softwarePHPGurukul Job Portal 1.0
Attack typesSQL Injection
Evidence & reasoningClassification basis · observed behavior · safety review
Technical evidence

Classification basis and observed behavior

Classification basis

The artifact is a README file providing a technical analysis of SQL injection vulnerabilities, including vulnerable code snippets, example payloads, and setup instructions. It does not contain any executable exploit or scanner code; the files 'exploit/sqli_payloads.txt' and 'docs/exploit-explanation.md' are listed as unavailable text files, so their content cannot be assessed. The README explicitly states it is a 'representative vulnerable implementation' for educational purposes, not the original affected software.

README.md:1-102

Requirements

  • Docker and Docker Compose must be installed to run the vulnerable environment.README.md:60-61

Observed behavior

  • The README describes a vulnerable login endpoint (login.php) that uses unsanitized user input in a SQL query, allowing authentication bypass with payloads like ' OR '1'='1' --.README.md:33-42
  • The README describes a vulnerable search endpoint (search.php) that uses unsanitized user input in a SQL query, allowing unauthorized data disclosure with payloads like %' OR '1'='1' --.README.md:44-55
  • The Dockerfile sets up a PHP 8.0 Apache environment with the mysqli extension, which is the runtime for the vulnerable application.Dockerfile:1-3
Safety-review evidence

Behaviors behind the backdoor verdict

Observables

Vulnerable Application
Payload withheldThe PoC is explicitly educational and contains intentional vulnerabilities, which is normal for a PoC and not a backdoor.README.md:14-20
Review boundaries

What the analysis did not establish

  • Two selected text files ('docs/exploit-explanation.md' and 'exploit/sqli_payloads.txt') are reported as unavailable as text and were not included in the evidence packet, so their content could not be analyzed.
  • The evidence packet contains only the README.md and Dockerfile; the actual application source code (e.g., login.php, search.php) is not included, so the described vulnerabilities cannot be verified against the code.
  • Only 2 of 17 text files were included in the evidence; 15 files were omitted.
  • Two selected text files (docs/exploit-explanation.md, exploit/sqli_payloads.txt) were unavailable as text and not reviewed.
  • Binary files were flagged as metadata-only and not analyzed.
Model interpretation

This review is limited to the supplied PoC code and context. It does not assert that the code works or is safe to execute.

Docker lab environments

1
GitHub

docker-compose.yml

19melek19/TheMisfits-CVE-2024-8465-SQLiCreated Vuln labCVE-2024-8465Compose · mixed

1 Compose manifest · 1 Dockerfile · 2 services

View exploit
Analysisdeepseek-v4-pro:cloud ·

Environment assessment

A Docker Compose environment with a PHP 8.0 Apache web service and a MySQL 5.7 database, intended as a vulnerable web application for demonstrating SQL injection.

docker-compose.yml:1-21Dockerfile:1-3README.md:1-102

Lab assessment

Vulnerability lab

The README explicitly states the repository is a Proof of Concept to demonstrate an SQL Injection vulnerability modeled after CVE-2024-8465, and the application code contains intentionally vulnerable SQL queries.

README.md:1-102app/login.php:14-17app/search.php:5-7
Lab shapeCompose · mixed
Services2
Compose manifests1
Dockerfiles1
Evidence & reasoningComponents · CVE assessment · exercise context · review boundaries
Components

Services and files described by the evidence

web

vulnerable PHP web application

A PHP 8.0 Apache service built from the local Dockerfile. It serves a web application with login, search, and user detail pages that contain intentional SQL injection vulnerabilities. It connects to the 'db' service and exposes port 80 mapped to host port 8080.

docker-compose.yml:3-10Dockerfile:1-3app/login.php:14-17app/search.php:5-7app/admin/user/controller.php:5

db

MySQL database

A MySQL 5.7 database service initialized with a SQL script that creates the 'app_db' database, 'users' and 'employees' tables, and inserts sample data. It uses root password 'root' and creates an 'appuser' with password 'apppass'.

docker-compose.yml:12-21database/init.sql:1-25
CVE assessment

How the supplied evidence relates each vulnerability

CVE-2024-8465

Insufficient evidence

The README states the application is a representative vulnerable implementation inspired by CVE-2024-8465, not the original affected software. No details of the original CVE are provided in the evidence, so the association cannot be verified.

README.md:1-102
Exercise context

Requirements and sequence described by the evidence

Prerequisites

  • Docker and Docker Compose must be installed to build and run the environment.README.md:55-57
  • The repository must be cloned and the user must navigate into the project directory.README.md:60-65
  • The environment is started with 'docker compose up --build'.README.md:68-69

Evidence-described exercise path

  1. Access the login page at http://localhost:8080/index.php.README.md:73-74
  2. Attempt a failed login with valid-looking credentials to observe normal behavior.README.md:82
  3. Perform SQL injection on the login form using payload "' OR '1'='1' --" to bypass authentication.README.md:83README.md:30-31
  4. Access the search page at http://localhost:8080/search.php and use SQL injection payload "%' OR '1'='1' --" to retrieve all employee records.README.md:76-77README.md:42-43
Safety-review evidence

Behaviors behind the stored safety assessment

No harmful behavior observed

All visible behavior is confined to the lab's own containers. The web service exposes port 8080 on the host, which is a documented requirement for accessing the vulnerable application. No evidence of host escape, external connections, persistence, credential theft, or destructive actions beyond the intended lab target is present.

docker-compose.yml:1-21README.md:1-102
Review boundaries

What the analysis did not establish

  • The packet does not include the original CVE-2024-8465 details, so the association cannot be verified.
  • The file docs/exploit-explanation.md is empty, providing no additional exploit documentation.
  • The file exploit/sqli_payloads.txt is empty, providing no payload examples beyond the README.
Model interpretation

This review is limited to the supplied lab evidence packet. It does not assert that the environment runs, reproduces a vulnerability, or is safe to execute. Contract: eip-docker-lab-analysis-v1.

References

2