Extraction crash via out-of-bounds CopyString write
Published Jul 1, 2021 · Updated Aug 5, 2024
Heap-based buffer overflow in UnRAR 5.6.1.2 and 5.6.1.3 allows context-dependent attackers to crash extraction via a crafted RAR archive. Unpack::CopyString writes one byte beyond its heap buffer while Unpack::Unpack5 decodes attacker-controlled archive data. The archive must be extracted; public evidence confirms memory corruption and a process crash but does not demonstrate code execution.
Summary
What happened
Heap-based buffer overflow in UnRAR 5.6.1.2 and 5.6.1.3 allows context-dependent attackers to crash extraction via a crafted RAR archive. Unpack::CopyString writes one byte beyond its heap buffer while Unpack::Unpack5 decodes attacker-controlled archive data. The archive must be extracted; public evidence confirms memory corruption and a process crash but does not demonstrate code execution.
The record
- CVE
- CVE-2017-20006
- Published
- Jul 1, 2021
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 1, 2021CVE publishedPublication date reported by the CVE source.
- Aug 5, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- OSS-Fuzz Unpack::CopyString crash reportproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo