Code execution via unchecked calloc multiplication
Published May 3, 2022 · Updated Apr 16, 2025
Integer overflow in calloc in RIOT OS 2020.01.1 allows remote attackers to crash devices or execute code through crafted allocations. Its calloc implementation multiplies the element count by element size without checking for wraparound, then allocates the resulting undersized buffer. Exploitation requires control of both calloc arguments and subsequent memory accesses; resulting memory corruption can crash the device or execute injected code.
Summary
What happened
Integer overflow in calloc in RIOT OS 2020.01.1 allows remote attackers to crash devices or execute code through crafted allocations. Its calloc implementation multiplies the element count by element size without checking for wraparound, then allocates the resulting undersized buffer. Exploitation requires control of both calloc arguments and subsequent memory accesses; resulting memory corruption can crash the device or execute injected code.
The record
- CVE
- CVE-2021-27427
- Published
- May 3, 2022
- Updated
- Apr 16, 2025
- Vendor
- RIOT-OS
- Product
- RIOT OS
- Classifications
- CWE-190, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 3, 2022CVE publishedPublication date reported by the CVE source.
- Apr 16, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2020.01.1
What conditions does exploitation require?
What is affected?
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