Application crash via malformed CR3 EXIF metadata
Published Jun 28, 2020 · Updated Aug 4, 2024
Out-of-bounds write in LibRaw before 0.20-Beta3 allows attackers to crash image-processing applications via a crafted CR3 file. In parse_exif() in src/metadata/exif_gps.cpp, an unrecognized AtomName combined with a zero tiff_nifds value drives an out-of-range metadata write. Execution requires an application to process the crafted file; the demonstrated consequence is an access-violation crash, not data disclosure or modification.
Summary
What happened
Out-of-bounds write in LibRaw before 0.20-Beta3 allows attackers to crash image-processing applications via a crafted CR3 file. In parse_exif() in src/metadata/exif_gps.cpp, an unrecognized AtomName combined with a zero tiff_nifds value drives an out-of-range metadata write. Execution requires an application to process the crafted file; the demonstrated consequence is an access-violation crash, not data disclosure or modification.
The record
- CVE
- CVE-2020-15365
- Published
- Jun 28, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 28, 2020CVE 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?
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.
Weakness, pattern, technique
Public exploit references
- Crafted CR3 proof of conceptproof 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