Memory disclosure or crash via short MSP430 input
Published May 13, 2022 · Updated Aug 3, 2024
Out-of-bounds read in radare2 before 5.7.0 allows local users to read process memory or crash the tool with a crafted MSP430 binary. The MSP430 disassembler's msp430_op function reads a two-byte call operand from buf at offset 2 without first verifying sufficient input length. Exploitation requires an affected local installation to analyze the malformed instruction stream, and the reported consequences are limited to memory disclosure or a process crash.
Summary
What happened
Out-of-bounds read in radare2 before 5.7.0 allows local users to read process memory or crash the tool with a crafted MSP430 binary. The MSP430 disassembler's msp430_op function reads a two-byte call operand from buf at offset 2 without first verifying sufficient input length. Exploitation requires an affected local installation to analyze the malformed instruction stream, and the reported consequences are limited to memory disclosure or a process crash.
The record
- CVE
- CVE-2022-1714
- Published
- May 13, 2022
- Updated
- Aug 3, 2024
- Vendor
- radareorg
- Product
- radare2
- Classifications
- CWE-125
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- May 13, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <5.7.0
What conditions does exploitation require?
What is affected?
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
- huntr.dev proof-of-concept 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