Heap overwrite via undersized insert_many allocation
Published Jan 22, 2021 · Updated Aug 3, 2024
Heap-based buffer overflow in smallvec 0.6.3 through 0.6.13 and 1.0.0 through 1.6.0 allows attackers to corrupt memory via insert_many. The method allocates from the iterator's size_hint lower bound, then writes every yielded item without reserving space for excess items. Triggering requires an iterator that yields more items than that lower bound, causing an out-of-bounds heap write and memory corruption.
Summary
What happened
Heap-based buffer overflow in smallvec 0.6.3 through 0.6.13 and 1.0.0 through 1.6.0 allows attackers to corrupt memory via insert_many. The method allocates from the iterator's size_hint lower bound, then writes every yielded item without reserving space for excess items. Triggering requires an iterator that yields more items than that lower bound, causing an out-of-bounds heap write and memory corruption.
The record
- CVE
- CVE-2021-25900
- Published
- Jan 22, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 22, 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.
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