Boot memory-range bypass via image-length overflow
Published Feb 19, 2024 · Updated Aug 1, 2024
Integer overflow in Renesas R-Car Gen3 v2.5 allows physically proximate attackers to bypass a BL2 memory-range check. BL2 multiplies the certificate-supplied image length by four in a 32-bit unsigned value, then uses the wrapped result to validate the destination range. Flash-area write access and specialized equipment are required; ASRG reports that the same overflow recurs during copying, so no out-of-bounds write or present security risk is demonstrated.
Summary
What happened
Integer overflow in Renesas R-Car Gen3 v2.5 allows physically proximate attackers to bypass a BL2 memory-range check. BL2 multiplies the certificate-supplied image length by four in a 32-bit unsigned value, then uses the wrapped result to validate the destination range. Flash-area write access and specialized equipment are required; ASRG reports that the same overflow recurs during copying, so no out-of-bounds write or present security risk is demonstrated.
The record
- CVE
- CVE-2024-1633
- Published
- Feb 19, 2024
- Updated
- Aug 1, 2024
- Vendor
- Renesas Electronics
- Product
- R-Car Gen3
- Classifications
- CWE-190, CAPEC-92, T1542.001
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 19, 2024CVE publishedPublication date reported by the CVE source.
- Aug 1, 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=v2.5
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