Application crash via unchecked SRF metadata offsets
Published Sep 1, 2022 · Updated Aug 4, 2024
Out-of-bounds reads in LibRaw 0.20-RC2 through 0.20.2 and 0.21-Beta1 allow context-dependent attackers to crash applications via SRF files. LibRaw::parseSonySRF passes file-controlled tag offsets to four-byte reads without first ensuring that the referenced bytes remain inside the allocated SRF buffer. An application must process a crafted SRF file; the published reproducer shows a crash, with no reported data disclosure or code execution.
Summary
What happened
Out-of-bounds reads in LibRaw 0.20-RC2 through 0.20.2 and 0.21-Beta1 allow context-dependent attackers to crash applications via SRF files. LibRaw::parseSonySRF passes file-controlled tag offsets to four-byte reads without first ensuring that the referenced bytes remain inside the allocated SRF buffer. An application must process a crafted SRF file; the published reproducer shows a crash, with no reported data disclosure or code execution.
The record
- CVE
- CVE-2020-35535
- Published
- Sep 1, 2022
- Updated
- Aug 4, 2024
- Vendor
- LibRaw LLC
- Product
- LibRaw
- Classifications
- CWE-125, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 1, 2022CVE publishedPublication date reported by the CVE source.
- Aug 4, 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=LibRaw 0.21-Beta1, LibRaw 0.20.2, LibRaw 0.20.1, LibRaw 0.20.0, LibRaw 0.20-RC2
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.
Public exploit references
- Crafted SRF crash reproducerproof 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