Decompression crash via error-tagged result pointer
Published Mar 19, 2021 · Updated Dec 17, 2025
Improper error handling in BusyBox 1.32.1 and earlier allows remote attackers to crash gzip decompression with malformed data. In decompress_gunzip.c, huft_build can encode an error in the low bit of its result pointer, but the cleanup path treats the tagged value as a valid allocation and attempts to free it. Exploitation requires BusyBox to process attacker-supplied gzip content; the bounded consequence is an invalid free or segmentation fault in the decompression process.
Summary
What happened
Improper error handling in BusyBox 1.32.1 and earlier allows remote attackers to crash gzip decompression with malformed data. In decompress_gunzip.c, huft_build can encode an error in the low bit of its result pointer, but the cleanup path treats the tagged value as a valid allocation and attempts to free it. Exploitation requires BusyBox to process attacker-supplied gzip content; the bounded consequence is an invalid free or segmentation fault in the decompression process.
The record
- CVE
- CVE-2021-28831
- Published
- Mar 19, 2021
- Updated
- Dec 17, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-755, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 19, 2021CVE publishedPublication date reported by the CVE source.
- Dec 17, 2025Record 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
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