mariadb
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-10CVE-2022-23940 has a selected CVSS score of 8.8 (high); EIP currently links 1 repository PoC and 1 lab environment.
SuiteCRM through 7.12.1 and 8.x through 8.0.1 allows Remote Code Execution. Authenticated users with access to the Scheduled Reports module can achieve this by leveraging PHP deserialization in the email_recipients property. By using a crafted request, they can create a malicious report, containing a PHP-deserialization payload in the email_recipients field. Once someone accesses this report, the backend will deserialize the content of the email_recipients field and the payload gets executed. Project dependencies include a number of interesting PHP deserialization gadgets (e.g., Monolog/RCE1 from phpggc) that can be used for Code Execution.
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-6The 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-32MariaDB 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-10SuiteCRM 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-26Insufficient 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-32vulnerable/docker-compose.yml:1vulnerable/docker-compose.yml:13-14vulnerable/README.md:5-6The 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-6This 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.