Service interruption via unbounded screen allocation
Published Jun 14, 2022 · Updated Aug 4, 2024
Memory exhaustion in gif2rgb in GIFLIB 5.1.4 allows remote attackers to interrupt service by supplying a crafted GIF file. The GIF2RGB routine trusts attacker-controlled logical-screen dimensions and allocates a full screen buffer before validating later records, so a 32-byte image declaring 65,503 by 65,503 pixels consumes about 4 GiB. Processing the file with the command-line utility is required; the upstream issue reports system-wide memory exhaustion and process termination, not confidentiality or integrity loss.
Summary
What happened
Memory exhaustion in gif2rgb in GIFLIB 5.1.4 allows remote attackers to interrupt service by supplying a crafted GIF file. The GIF2RGB routine trusts attacker-controlled logical-screen dimensions and allocates a full screen buffer before validating later records, so a 32-byte image declaring 65,503 by 65,503 pixels consumes about 4 GiB. Processing the file with the command-line utility is required; the upstream issue reports system-wide memory exhaustion and process termination, not confidentiality or integrity loss.
The record
- CVE
- CVE-2021-40633
- Published
- Jun 14, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 14, 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?
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
- out-of-memory-expection-or-memory-leak.gifproof 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