CVE-2023-40477
Rarlab Winrar ≤ 6.23
Raw vector
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2023-40477 is a high-severity Improper Validation of Array Index (CWE-129) vulnerability in Rarlab Winrar. Its CVSS base score is 7.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 4% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
RARLAB WinRAR contains an improper validation of array index vulnerability (CWE-129) in its handling of recovery volumes. The flaw permits an out-of-bounds memory access when processing specially crafted recovery data, enabling remote code execution on affected installations. The issue was originally reported as ZDI-CAN-21233 and carries a CVSS 3.0 score of 7.8.
Remote attackers can trigger the vulnerability by supplying a malicious recovery volume that a user must open or that is reached via a malicious web page. Successful exploitation grants arbitrary code execution in the context of the current WinRAR process; no privileges are required beyond normal user interaction with the file.
Vendor advisories and the Zero Day Initiative disclosure point to updated WinRAR builds that correct the recovery-volume processing logic. The Debian LTS announcement similarly references backported fixes for supported releases. EPSS scores remain elevated near 0.92, indicating sustained exploitation interest following public disclosure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-45048
Vulnerability Data
RARLAB WinRAR Recovery Volume Improper Validation of Array Index Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of RARLAB WinRAR. User interaction is required to exploit this vulnerability in that the target…
more
must visit a malicious page or open a malicious file. The specific flaw exists within the processing of recovery volumes. The issue results from the lack of proper validation of user-supplied data, which can result in a memory access past the end of an allocated buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-21233.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require input validation and bounds checking that prevent improper array indexing.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development can detect out-of-bounds array access but does not prevent the weakness by itself.
Secure development lifecycle mandates input validation and bounds checking that directly prevents improper array indexing.
Application security requirements include validation of untrusted input used for indexing or addressing memory structures.
Secure architecture principles encourage defensive coding patterns that reduce index-related vulnerabilities.
Secure coding standards explicitly require bounds checking and validation of array indices derived from untrusted data.