dbcve.org
CommonApplication · Containers

CVE-2024-9341

HIGH · 8.2 CVSS v3.1 Published 2024-10-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
89/100
Remediation priority · High
Remotely reachable No privileges

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 · unedited
A flaw was found in Go. When FIPS mode is enabled on a system, container runtimes may incorrectly handle certain file paths due to improper validation in the containers/common Go library. This flaw allows an attacker to exploit symbolic links and trick the system into mounting sensitive host directories inside a container. This issue also allows attackers to access critical host files, bypassing the intended isolation between containers and the host system.

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 confidence

A path validation vulnerability exists in the containers/common Go library when FIPS mode is enabled. The library fails to properly validate file paths, allowing attackers to exploit symbolic links to mount sensitive host directories into containers or access critical host files, thereby escaping container isolation.

MitigationUpdate containers/common to the patched version that properly validates paths and resolves symbolic links before mounting. Ensure FIPS-enabled systems have additional path validation checks in container runtime configurations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CommonApplication
Affected:all versions
Openshift Container PlatformApplication
Affected:= 4.12= 4.13= 4.14= 4.15= 4.16= 4.17
Enterprise LinuxOperating system
Affected:= 8.0= 9.0

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
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify FIPS mode is enabled on the host
    Check system FIPS status by examining /proc/sys/crypto/fips_enabled or running 'fips-mode-setup --check' if the tool is available. On RHEL systems, also check 'cryptsetup isLuks' output or review /etc/crypttab for FIPS configurations.
    Affected if FIPS mode is enabled - this vulnerability only applies when FIPS mode is active on the system
  2. Identify the installed containers/common version
    Run 'rpm -q containers-common' on RHEL-based systems, or use 'go list -m all' if working from source. On systems with podman, 'podman info' may also reveal container library versions.
    Affected if Any version of containers/common is installed and FIPS mode is enabled - all versions are affected according to the advisory
  3. Confirm the host operating system and version
    Check the OS version using 'cat /etc/os-release' or 'hostnamectl'. Identify if it is Red Hat Enterprise Linux 8.0, 9.0, or if OpenShift Container Platform versions 4.12 through 4.17 are in use.
    Affected if The system is RHEL 8.0, RHEL 9.0, or OCP 4.12-4.17 with FIPS enabled and containers/common in use
  4. Determine if container volume mounts using host paths are in use
    Review container orchestration configurations, docker-compose files, podman run commands, or kubernetes pod specs for volume mount definitions that reference host directories (hostPath volumes or -v /host/path:container/path flags).
    Affected if Container volume mounts that could leverage symbolic links to escape isolation are configured and the system meets the affected version criteria

The environment is affected if FIPS mode is enabled AND containers/common is in use on any of the specified Red Hat product versions, particularly when container volume mounts from host paths are configured.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update containers/common to the patched version that properly validates paths and resolves symbolic links before mounting. Ensure FIPS-enabled systems have additional path validation checks in container runtime configurations.

Recommended fix Moderate confidence

OpenShift Container Platform: update to the latest z-stream release within your minor version (4.12.x, 4.13.x, 4.14.x, or 4.15.x) that includes the security fix; Enterprise Linux: update to the latest containers/common package available in the RHEL 8 or 9 repos

  1. Check the Red Hat security advisory (RHSA) for CVE-2024-9341 at access.redhat.com for your specific product version
  2. For OpenShift Container Platform: Apply the corresponding OCP update for your version (4.12, 4.13, 4.14, or 4.15) via the ocp adm upgrade command or by updating the corresponding package manifests
  3. For Enterprise Linux: Update the containers/common package via 'dnf update' or 'yum update' to receive the patched version
  4. After updating, verify that the containers/common library version matches the patched version specified in the RHSA
  5. Test container isolation to confirm the symlink vulnerability is resolved
  6. For FIPS-enabled systems, ensure the updated runtime properly validates file paths before container mounting
Caveat No major breaking changes expected from this security patch; minor version updates should maintain compatibility

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Common Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-9341 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-9341 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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