Advanced Cluster SecurityApplication · Redhat
CVE-2024-0406
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 flaw was discovered in the mholt/archiver package. This flaw allows an attacker to create a specially crafted tar file, which, when unpacked, may allow access to restricted files or directories. This issue can allow the creation or overwriting of files with the user's or application's privileges using the library.
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 · moderate confidenceThe mholt/archiver package contains a path traversal vulnerability in tar file extraction. Specially crafted tar archives containing entries with relative path traversal sequences (e.g., ../../etc/passwd) can cause files to be extracted outside the intended target directory, allowing attackers to overwrite or create files with the application's privileges.
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
Advanced Cluster SecurityApplication
= 3.0
Openshift Container PlatformApplication
>= 4.18, < 4.18.4>= 3.0.0, < 4.0.0CVSS 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
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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.
-
Locate mholt/archiver package usageSearch your codebase or dependency manifests (go.mod, go.sum, vendor directory, container image layers) for the import 'github.com/mholt/archiver' or package 'mholt/archiver'Affected if The package is found in your dependencies or codebase
-
Identify the installed archiver versionExamine the version constraint in go.mod or the actual version in go.sum/vendor; compare the installed version against the affected range of >= 3.0.0 and < 4.0.0Affected if The installed version falls within >= 3.0.0, < 4.0.0
-
Find tar extraction code pathsSearch your codebase for calls to archiver.TarArchive, archiver.Unarchive, or any custom extraction routines that use the archiver package to handle tar filesAffected if Code exists that extracts tar archives using the mholt/archiver package
-
Inspect extraction logic for path validationReview the tar extraction code to determine if it performs path validation checks (such as resolving paths and comparing against the target directory, or rejecting entries with '..' sequences) before writing filesAffected if The extraction code does NOT validate that resolved paths stay within the target directory, or no such validation is found
Your environment is affected if mholt/archiver version 3.0.0 through below 4.0.0 is used and your code performs tar extraction without validating that extracted file paths resolve within the intended target directory.
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 data4.0.04.18.4
Implement strict path validation during archive extraction to ensure extracted file paths resolve within the target directory. Reject any archive entries that would escape the intended extraction directory.
Fix this in Advanced Cluster Security
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0406 — 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-2024-0406 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