Code execution via unchecked allocation-size addition
Published Nov 21, 2023 · Updated Aug 3, 2024
Integer overflow in TI SimpleLink SDK FreeRTOS POSIX malloc allows local users to execute code through an oversized allocation request. The source/ti/posix/freertos/memory.c malloc adds sizeof(Header) to the requested size without detecting wraparound, then returns a valid pointer to an undersized buffer. Exploitation requires control of the function size argument, typically through another flaw, and subsequent writes can corrupt the heap and redirect execution.
Summary
What happened
Integer overflow in TI SimpleLink SDK FreeRTOS POSIX malloc allows local users to execute code through an oversized allocation request. The source/ti/posix/freertos/memory.c malloc adds sizeof(Header) to the requested size without detecting wraparound, then returns a valid pointer to an undersized buffer. Exploitation requires control of the function size argument, typically through another flaw, and subsequent writes can corrupt the heap and redirect execution.
The record
- CVE
- CVE-2021-27504
- Published
- Nov 21, 2023
- Updated
- Aug 3, 2024
- Vendor
- Texas Instruments
- Product
- SimpleLink CC26xx SDK
- Classifications
- CWE-190
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 21, 2023CVE 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <4.40.00
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