Application crash via unchecked BMP row writes
Published May 24, 2020 · Updated Aug 4, 2024
Out-of-bounds write in ffjpeg through 2020-02-24 allows remote attackers to crash the codec by supplying a crafted BMP file. The bmp_load function trusts header-derived dimensions when calculating the row stride and destination pointer, then reads each row without ensuring that the write remains within the allocated pixel buffer. Execution requires a user or calling application to process the crafted file; the demonstrated consequence is a SIGSEGV service interruption.
Summary
What happened
Out-of-bounds write in ffjpeg through 2020-02-24 allows remote attackers to crash the codec by supplying a crafted BMP file. The bmp_load function trusts header-derived dimensions when calculating the row stride and destination pointer, then reads each row without ensuring that the write remains within the allocated pixel buffer. Execution requires a user or calling application to process the crafted file; the demonstrated consequence is a SIGSEGV service interruption.
The record
- CVE
- CVE-2020-13440
- Published
- May 24, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 24, 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.
Public exploit references
- segv_ffjpeg_e1 crafted BMP testcasefunctional · 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