Enterprise Linux DesktopOperating system · Redhat
CVE-2014-8140
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 · uneditedHeap-based buffer overflow in the test_compr_eb function in Info-ZIP UnZip 6.0 and earlier allows remote attackers to execute arbitrary code via a crafted zip file in the -t command argument to the unzip command.
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 confidenceHeap-based buffer overflow in the test_compr_eb function of Info-ZIP UnZip 6.0 and earlier allows arbitrary code execution when processing a crafted zip file via the -t (test) command argument.
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
Enterprise Linux DesktopOperating system
= 6.0= 7.0
Enterprise Linux ServerOperating system
= 6.0= 7.0
Enterprise Linux Server AusOperating system
= 6.6= 7.3= 7.4= 7.6= 7.7
Enterprise Linux Server EusOperating system
= 6.6= 7.1= 7.2= 7.3= 7.4= 7.5= 7.6= 7.7
Enterprise Linux Server TusOperating system
= 6.6= 7.3= 7.6= 7.7
Enterprise Linux WorkstationOperating system
= 6.0= 7.0<= 6.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.
-
Identify installed unzip versionRun 'unzip -v' or 'unzip --version' to display version informationAffected if Version displayed is 6.0 or earlier
-
Check for unzip package via package managerOn RHEL systems, run 'rpm -q unzip' and note the version number in the outputAffected if Package version is 6.0 or earlier based on the package name or 'rpm -qi unzip' version field
-
Identify scripts or automation using -t flagSearch for files containing 'unzip -t' or 'unzip -t ' (with space) using: 'grep -r "unzip -t" /path/to/search' or 'grep -r "unzip.*-t" /path/to/search'Affected if Any scripts, cron jobs, or automation pipelines invoke unzip with the -t argument on zip files
-
Assess exposure to untrusted zip filesReview log files, download directories, or intake folders where zip files from external sources are stored; check if any recent zip files were processed with unzip -tAffected if The environment processes zip files from untrusted or external sources using the unzip utility with the -t flag
You are affected if unzip version 6.0 or earlier is installed AND zip files are processed using the -t (test) argument, especially with untrusted or externally-sourced zip archives.
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 dataUpgrade to UnZip 6.1 or later which contains the patched version, or ensure untrusted zip files are not processed with the -t flag in vulnerable versions.
Fix this in Enterprise Linux Desktop
Scoped from the published advisory
- Consultation4.0 h
- Implementation2.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 $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-8140 — 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-2014-8140 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