CVE-2025-58712
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA container privilege escalation flaw was found in certain AMQ Broker images. This issue stems from the /etc/passwd file being created with group-writable permissions during build time. In certain conditions, an attacker who can execute commands within an affected container, even as a non-root user, can leverage their membership in the root group to modify the /etc/passwd file. This could allow the attacker to add a new user with any arbitrary UID, including UID 0, leading to full root privileges within the container.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA container privilege escalation vulnerability exists in certain AMQ Broker images where the /etc/passwd file is created with group-writable permissions (likely 0644) during the image build process. An attacker with the ability to execute commands inside an affected container as a non-root user who is a member of the root group (GID 0) can modify /etc/passwd to add a new account with UID 0, thereby gaining full root privileges within the container.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- High
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if /etc/passwd has group-writable permissionsRun 'ls -la /etc/passwd' inside the container and examine the group permissions (the second 'rw-' field). If the group permission includes 'w' (e.g., 0646, 0664), the file is group-writable.Affected if The group permission field shows 'rw-' or 'rwx' (e.g., permissions like 0646, 0664) rather than 'r--' (e.g., 0644)
-
Identify non-root users in the containerRun 'cat /etc/passwd' to list all users, then check which users have a non-zero UID (non-root). For each such user, run 'id <username>' or 'id' when logged in as that user to see their group memberships.Affected if There exists a user with UID > 0 whose primary or supplementary groups include GID 0 (root group)
-
Determine if running AMQ Broker containerCheck the container image by running 'cat /etc/os-release' or inspecting labels: 'docker inspect <container_id> --format "{{.Config.Labels}}"' or check for 'amq-broker' in the image name.Affected if The container is running an AMQ Broker image (from Red Hat or Apache ActiveMQ)
-
Check if user is member of root group (GID 0)If you can execute commands as a specific user inside the container, run 'id' to see group memberships. Alternatively, parse /etc/group for 'root:x:0:' and check which users are listed there.Affected if Any non-root user (UID > 0) is a member of the root group (GID 0)
The environment is affected if this is an AMQ Broker container where /etc/passwd has group-write permissions AND a non-root user with access to the container is a member of the root group (GID 0).
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRebuild the affected container images with corrected /etc/passwd permissions (remove group-write bit, typically chmod 644 /etc/passwd) in the Dockerfile or entrypoint script, and ensure non-root container users are not added to the root group.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58712 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-58712 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data