Process crash via unchecked in-memory GIF copy
Published Aug 27, 2021 · Updated Aug 4, 2024
Heap-buffer overflow in ngiflib 0.4 allows remote attackers to crash a consuming process through a crafted GIF decoded from memory. In NGIFLIB_NO_FILE mode, GetByteStr() calls memcpy for the requested byte count without confirming that the input buffer contains enough bytes. Exploitation requires a consuming application built with NGIFLIB_NO_FILE to process the supplied GIF; the published proof demonstrates an out-of-bounds read and AddressSanitizer abort.
Summary
What happened
Heap-buffer overflow in ngiflib 0.4 allows remote attackers to crash a consuming process through a crafted GIF decoded from memory. In NGIFLIB_NO_FILE mode, GetByteStr() calls memcpy for the requested byte count without confirming that the input buffer contains enough bytes. Exploitation requires a consuming application built with NGIFLIB_NO_FILE to process the supplied GIF; the published proof demonstrates an out-of-bounds read and AddressSanitizer abort.
The record
- CVE
- CVE-2021-36530
- Published
- Aug 27, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 27, 2021CVE 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
- poc-ngiflib-0245fd4-GetByteStr-overflowproof 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