manuelz120/CVE-2022-23940

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

vulnerable/docker-compose.yml

Created Vuln labCVE-2022-23940Compose · images

1 Compose manifest · 2 services

Analysisdeepseek-v4-pro:cloud ·

Environment assessment

A Docker Compose environment defining a SuiteCRM 7.11.8 instance with a MariaDB 10.3 database, exposing HTTP/HTTPS ports. The README labels it as a vulnerable instance and provides credentials.

vulnerable/docker-compose.yml:1-32vulnerable/README.md:1-6

Lab assessment

Vulnerability lab

The README explicitly states 'Vulnerable SCRM Instance' and the repository is named after CVE-2022-23940, indicating a deliberate vulnerability research or reproduction environment.

vulnerable/README.md:1vulnerable/docker-compose.yml:1-32
Lab shapeCompose · images
Services2
Compose manifests1
Dockerfiles0
Evidence & reasoningComponents · CVE assessment · exercise context · review boundaries
Components

Services and files described by the evidence

mariadb

database

MariaDB 10.3 service using the Bitnami image, configured with empty password allowed, a user 'bn_suitecrm', and a database 'bitnami_suitecrm'. Data persisted via named volume.

vulnerable/docker-compose.yml:3-10

suitecrm

web applicationvulnerable target

SuiteCRM 7.11.8 service using the Bitnami image, exposing ports 80 and 443, connected to the mariadb service. Configured with empty password allowed. Data persisted via named volume. Depends on mariadb.

vulnerable/docker-compose.yml:11-26
CVE assessment

How the supplied evidence relates each vulnerability

CVE-2022-23940

Insufficient evidence

The repository name and README reference CVE-2022-23940, but the supplied evidence (Compose file and README) does not contain any details about the vulnerability, its reproduction steps, or how the environment demonstrates it. The association is based solely on naming, not on visible behavior or configuration.

vulnerable/README.md:1vulnerable/docker-compose.yml:1-32
Exercise context

Requirements and sequence described by the evidence

Prerequisites

  • Docker and Docker Compose must be installed to run the environment.vulnerable/docker-compose.yml:1
  • The SuiteCRM instance is accessible on host ports 80 and 443.vulnerable/docker-compose.yml:13-14
  • Credentials 'user' / 'bitnami' are provided for the SuiteCRM instance.vulnerable/README.md:5-6
Safety-review evidence

Behaviors behind the stored safety assessment

Insufficient evidence

The evidence only shows a standard Docker Compose setup for a vulnerable SuiteCRM instance. No exploit code, scripts, or instructions are included. The environment does not exhibit any behavior beyond exposing the application on host ports, which is expected for a lab. However, without any exercise steps or exploit payloads, the safety of the intended use cannot be fully assessed.

vulnerable/docker-compose.yml:1-32vulnerable/README.md:1-6
Review boundaries

What the analysis did not establish

  • No exploit code, scripts, or detailed vulnerability reproduction steps are included in the packet.
  • The CVE association is based solely on repository naming; no technical details about CVE-2022-23940 are present.
  • The requirements.txt file is present in the repository but not part of the unit; its role is unclear.
  • The packet contains only static configuration; runtime behavior cannot be observed.
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