Debian LinuxOperating system · Debian
CVE-2017-14122
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 · uneditedunrar 0.0.1 (aka unrar-free or unrar-gpl) suffers from a stack-based buffer over-read in unrarlib.c, related to ExtrFile and stricomp.
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 confidenceunrar-free (unrar-gpl) 0.0.1 contains a stack-based buffer over-read vulnerability in unrarlib.c within the ExtrFile and stricomp functions. This memory safety issue allows reading beyond buffer boundaries on the stack, potentially exposing sensitive data or facilitating code execution given the critical CVSS score of 9.1.
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
Debian LinuxOperating system
= 9.0= 0.0.1CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 unrar-free is installedRun `which unrar-free` or check your package manager for the unrar-free packageAffected if unrar-free is found on the system
-
Determine installed version of unrar-freeRun `unrar-free --version` or query your package manager for the installed version (e.g., `dpkg -l unrar-free` on Debian)Affected if Version is 0.0.1
-
Verify the presence of the vulnerable libraryCheck for the presence of unrarlib.c compiled library or the unrar-free binary that contains the ExtrFile and stricomp functionsAffected if The binary/library from unrar-free 0.0.1 is in use
-
Check if RAR files are being processedMonitor or audit processes that invoke unrar-free to extract RAR archivesAffected if unrar-free is actively used to extract RAR archives
-
Confirm strictcmp function usage in code or configIf compiling from source, verify that unrarlib.c containing the stricomp function is included in the buildAffected if The vulnerable code path (stricomp/ExtrFile) is reachable
The environment is affected if unrar-free version 0.0.1 is installed and being used to process RAR files, as the stack-based buffer over-read in the ExtrFile and stricomp functions will be triggered during archive extraction.
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 a patched version of unrar-free if available; if unrar-free is unmaintained, migrate to an actively maintained RAR extraction alternative such as unar or the official WinRAR RAR5 utility.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation2.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 $3,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14122 — 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-2017-14122 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