Heap corruption via wrapped allocation size
Published Feb 19, 2025 · Updated Feb 19, 2025
Integer overflow in barebox before 2025.01.0 allows physically proximate attackers to obtain an undersized heap allocation. The request2size macro in common/dlmalloc.c adds allocator padding before validating the result, so a near-LONG_MAX request wraps and is reduced to the minimum chunk size. Exploitation requires control of an extreme allocation request through device-supplied input, and a caller that trusts the returned size can overwrite heap memory.
Summary
What happened
Integer overflow in barebox before 2025.01.0 allows physically proximate attackers to obtain an undersized heap allocation. The request2size macro in common/dlmalloc.c adds allocator padding before validating the result, so a near-LONG_MAX request wraps and is reduced to the minimum chunk size. Exploitation requires control of an extreme allocation request through device-supplied input, and a caller that trusts the returned size can overwrite heap memory.
The record
- CVE
- CVE-2024-57261
- Published
- Feb 19, 2025
- Updated
- Feb 19, 2025
- Vendor
- Pengutronix
- Product
- barebox
- Classifications
- CWE-190
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 19, 2025CVE publishedPublication date reported by the CVE source.
- Feb 19, 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=0 <2025.01.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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