libasmon/Exploite-CVE-2023-30212-Vulnerability

GitHubRepository PoC

PoC files

8 files

File viewing is interactive and short-lived. Downloads are password-protected ZIP archives using password eip.

GitHub

Docker lab environments

1
GitHub

Repository root

Created Vuln labCVE-2023-30212Dockerfile

1 Dockerfile

Analysisdeepseek-v4-pro:cloud ·

Environment assessment

A single Dockerfile based on php:7.2-apache that installs MySQL, creates a 'test' database, copies local application files, and starts Apache and MySQL. The README describes it as a vulnerable Docker environment for CVE-2023-30212, an XSS vulnerability in OURPHP <= 7.2.0.

dockerfile:1-52README.md:1-4

Lab assessment

Vulnerability lab

The README explicitly states the purpose is to 'create a vulnerable Docker environment that is susceptible to CVE-2023-30212' and provides steps to build, run, and exploit the vulnerability. The Dockerfile sets up a PHP/Apache/MySQL stack consistent with hosting a vulnerable OURPHP application.

README.md:1-4
Lab shapeDockerfile
ServicesUnknown
Compose manifests0
Dockerfiles1
Evidence & reasoningComponents · CVE assessment · exercise context · review boundaries
Components

Services and files described by the evidence

php:7.2-apache base image

web serverPHP runtime

Official PHP 7.2 Apache image used as the base. Provides Apache with PHP support.

dockerfile:2

MySQL server

database server

Installed via apt-get, started to create a 'test' database, and started again in the CMD to run alongside Apache.

dockerfile:18-25dockerfile:50

Web application files

vulnerable application

Copied from a local 'file' directory into the Apache document root. The README references OURPHP and an exploit path, indicating these files contain the vulnerable OURPHP application.

dockerfile:37README.md:3-4
CVE assessment

How the supplied evidence relates each vulnerability

CVE-2023-30212

Insufficient evidence

The README claims the environment is susceptible to CVE-2023-30212 and provides an exploit URL. However, the actual application source code (e.g., ourphp_out.php) is not included in the evidence files, so the presence of the vulnerable code cannot be verified.

README.md:3-4README.md:75
Exercise context

Requirements and sequence described by the evidence

Prerequisites

  • Docker must be installed on the host to build and run the image.README.md:11-15
  • The local 'file' directory containing the OURPHP application must be present in the build context.dockerfile:37

Evidence-described exercise path

  1. Build the Docker image using 'docker build -t test .'README.md:21-23
  2. Run the container with port mapping: 'docker run -d -p 8080:80 test'README.md:27-29
  3. Access the vulnerable URL: http://localhost:8080/client/manage/ourphp_out.php?ourphp_admin=logout&out=</script><script>alert(`xss`)</script>README.md:75
Safety-review evidence

Behaviors behind the stored safety assessment

No harmful behavior observed

The Dockerfile and README describe a self-contained lab environment. The only network exposure is port 80 mapped to the host, which is typical for a web-based vulnerability lab. No hidden or unnecessary host compromise, persistence, credential theft, or external connections are indicated.

dockerfile:1-52README.md:1-90
Review boundaries

What the analysis did not establish

  • The actual OURPHP application source files (e.g., ourphp_out.php) are not included in the evidence, so the vulnerability cannot be confirmed.
  • The Dockerfile COPY instruction references a 'file' source, but the file inventory shows no such directory; the build may fail if the directory is missing.
  • The README contains instructions to grant all privileges to 'root'@'localhost' with a password, which is a weak security practice but is presented as part of the lab setup.
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.

Linked vulnerabilities

1