Code execution via improperly initialized correction memory
Published Jan 14, 2020 · Updated Aug 6, 2024
Improper initialization in LibRaw before 0.17.1 allows attackers to trigger memory errors and possibly execute code via a crafted RAW image. The phase_one_correct function processes Phase One correction data without correctly initializing its memory objects and does not reliably return and propagate processing failures. Exploitation requires a consuming application to process attacker-supplied Phase One RAW data; the resulting corruption can crash the process or execute code.
Summary
What happened
Improper initialization in LibRaw before 0.17.1 allows attackers to trigger memory errors and possibly execute code via a crafted RAW image. The phase_one_correct function processes Phase One correction data without correctly initializing its memory objects and does not reliably return and propagate processing failures. Exploitation requires a consuming application to process attacker-supplied Phase One RAW data; the resulting corruption can crash the process or execute code.
The record
- CVE
- CVE-2015-8367
- Published
- Jan 14, 2020
- Updated
- Aug 6, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-665, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 14, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
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