Application crash via malformed recovery-volume filename
Published May 3, 2024 · Updated Nov 4, 2025
Buffer overflow in WinRAR before 6.23 allows remote attackers to crash the application by inducing a user to unpack crafted recovery files. The old RAR 3.0 recovery-volume path processes a malformed REV filename without adequate bounds validation, overwriting the buffer edge with C++ object pointers. Exploitation requires a RAR file and malformed REV file in the same folder plus user-initiated unpacking; RARLAB reports no demonstrated code execution.
Summary
What happened
Buffer overflow in WinRAR before 6.23 allows remote attackers to crash the application by inducing a user to unpack crafted recovery files. The old RAR 3.0 recovery-volume path processes a malformed REV filename without adequate bounds validation, overwriting the buffer edge with C++ object pointers. Exploitation requires a RAR file and malformed REV file in the same folder plus user-initiated unpacking; RARLAB reports no demonstrated code execution.
The record
- CVE
- CVE-2023-40477
- Published
- May 3, 2024
- Updated
- Nov 4, 2025
- Vendor
- RARLAB
- Product
- WinRAR
- Classifications
- CWE-129, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 3, 2024CVE publishedPublication date reported by the CVE source.
- Nov 4, 2025Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.21
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
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