LiveActive security incident?Get immediate response
CVE Record

CVE-2017-20006: UnRAR 5.6.1.2 and 5.6.1.3 has a heap-based buffer overflow in Unpack::CopyString (called from Unpack::Unpac...

UnRAR 5.6.1.2 and 5.6.1.3 has a heap-based buffer overflow in Unpack::CopyString (called from Unpack::Unpack5 and CmdExtract::ExtractCurrentFile).

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

UnRAR 5.6.1.2 and 5.6.1.3 may mishandle a RAR archive and corrupt heap memory during extraction. Business risk depends on whether affected UnRAR code processes untrusted archives, such as user uploads, email attachments, or downloaded files.

Executive priority

Treat this as an inventory and containment task unless affected UnRAR versions process untrusted archives. Prioritize remediation in automated extraction paths because they can convert a file-parsing flaw into operational exposure.

Technical view

CVE-2017-20006 is a heap-based buffer overflow in UnRAR's Unpack::CopyString, reached from Unpack::Unpack5 and CmdExtract::ExtractCurrentFile. The source bundle names affected versions 5.6.1.2 and 5.6.1.3, with OSS-Fuzz and a source commit referenced.

Likely exposure

Exposure is most likely where UnRAR 5.6.1.2 or 5.6.1.3 is installed or embedded and processes untrusted RAR files. The bundle does not identify downstream packages, platforms, appliances, or CPEs.

Exploitation context

No cited source states active exploitation, and KEV is false. The OSS-Fuzz reference suggests malformed archive input can trigger memory corruption during extraction, but the bundle does not establish real-world exploitation or reliable code execution.

Researcher notes

The public bundle lacks CVSS, CWE, CPE, downstream impact, and exploitability detail. Analysis should stay tied to the named UnRAR versions, affected function path, OSS-Fuzz issue, and referenced commit until vendor-specific advisories add evidence.

Mitigation direction

  • Inventory UnRAR deployments and embedded copies across servers, endpoints, and scanning pipelines.
  • Check vendor or project guidance for fixed releases or backported patches.
  • Update affected UnRAR 5.6.1.2 and 5.6.1.3 builds where guidance confirms remediation.
  • Restrict processing of untrusted RAR files until affected extractors are remediated.
  • Run archive extraction with least privilege and isolation where operationally possible.

Validation and detection

  • Confirm UnRAR version strings on systems that extract RAR archives.
  • Review SBOMs and bundled third-party components for UnRAR 5.6.1.2 or 5.6.1.3.
  • Identify workflows that automatically unpack user-supplied, emailed, or downloaded RAR files.
  • Check logs for unexplained extractor crashes during RAR processing.
  • Track the referenced commit and vendor advisories for confirmed fix lineage.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2017-20006 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.