LiveActive security incident?Get immediate response
CVE Record

CVE-2021-34079: OS Command injection vulnerability in Mintzo Docker-Tester through 1.2.1 allows attackers to execute arbitr...

OS Command injection vulnerability in Mintzo Docker-Tester through 1.2.1 allows attackers to execute arbitrary commands via shell metacharacters in the 'ports' entry of a crafted docker-compose.yml file.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

Docker-Tester through 1.2.1 can run unintended operating-system commands if it processes a malicious docker-compose.yml file. The issue is tied to shell metacharacters in the ports entry. Business risk is mainly in development or CI workflows that test Docker Compose files from untrusted or pull-request sources.

Executive priority

Treat this as a targeted supply-chain and CI risk, not a broad internet-facing emergency based on available evidence. Prioritize environments that run Docker-Tester on untrusted compose files because arbitrary command execution could compromise build systems.

Technical view

CVE-2021-34079 is an OS command injection flaw in Mintzo Docker-Tester through 1.2.1. Public CVE text says crafted docker-compose.yml content can place shell metacharacters in the ports entry, causing arbitrary command execution. No CVSS score, CWE, confirmed fixed version, or affected CPE data is provided in the bundle.

Likely exposure

Exposure is most likely where the npm docker-tester package is used in CI, build automation, or developer tooling against externally supplied docker-compose.yml files.

Exploitation context

The bundle does not show KEV listing or active exploitation evidence. Exploitation appears to require Docker-Tester to process a crafted docker-compose.yml file; details beyond the ports-field command injection vector are not provided.

Researcher notes

Evidence is sparse: the CVE record gives the vulnerable version range and injection field, but no CVSS, CWE, patch statement, or exploit-in-the-wild confirmation. Validate impact in controlled review by tracing Docker-Tester use and input trust boundaries.

Mitigation direction

  • Inventory projects and pipelines using docker-tester through version 1.2.1.
  • Do not process untrusted docker-compose.yml files with vulnerable Docker-Tester versions.
  • Check the Checkmarx advisory and npm package page for current vendor guidance.
  • Replace, remove, or isolate Docker-Tester if no fixed version is confirmed.
  • Restrict CI permissions when testing third-party or pull-request Docker Compose files.

Validation and detection

  • Search package manifests and lockfiles for docker-tester dependency versions.
  • Review CI jobs for Docker-Tester execution on pull requests or external repositories.
  • Confirm whether docker-compose.yml inputs are trusted before testing.
  • Check the ports field handling against vendor advisory details without running exploit payloads.
  • Document compensating controls if the package remains in use.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

Container behavior lookup

The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-34079 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.