Code execution or crash via allocation-size overflow
Published May 3, 2021 · Updated Aug 3, 2024
Integer overflow in AWS FreeRTOS Kernel before 10.4.3 allows remote attackers to execute code or crash devices via oversized allocations. The pvPortMalloc implementations add allocator metadata and alignment padding to xWantedSize without first rejecting size_t wraparound, causing a large request to receive an undersized heap buffer. Exploitation requires application code to derive the allocation size from attacker-controlled input; the device and heap implementation determine the resulting code execution or crash.
Summary
What happened
Integer overflow in AWS FreeRTOS Kernel before 10.4.3 allows remote attackers to execute code or crash devices via oversized allocations. The pvPortMalloc implementations add allocator metadata and alignment padding to xWantedSize without first rejecting size_t wraparound, causing a large request to receive an undersized heap buffer. Exploitation requires application code to derive the allocation size from attacker-controlled input; the device and heap implementation determine the resulting code execution or crash.
The record
- CVE
- CVE-2021-32020
- Published
- May 3, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-119, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 3, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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
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