Stack memory corruption via inconsistent iterator bounds
Published Apr 1, 2021 · Updated Nov 19, 2024
Out-of-bounds write in stackvector before 1.0.9 allows attackers to corrupt stack memory through a malformed Iterator size hint. StackVec::extend validates capacity against the reported upper bound but writes up to the lower bound without enforcing their order. Exploitation requires a caller-supplied Iterator whose lower bound exceeds its upper bound, causing a stack overwrite and a crash or corrupted program state.
Summary
What happened
Out-of-bounds write in stackvector before 1.0.9 allows attackers to corrupt stack memory through a malformed Iterator size hint. StackVec::extend validates capacity against the reported upper bound but writes up to the lower bound without enforcing their order. Exploitation requires a caller-supplied Iterator whose lower bound exceeds its upper bound, causing a stack overwrite and a crash or corrupted program state.
The record
- CVE
- CVE-2021-29939
- Published
- Apr 1, 2021
- Updated
- Nov 19, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 1, 2021CVE publishedPublication date reported by the CVE source.
- Nov 19, 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
- IncorrectIterator size_hint proof of conceptproof of concept · demonstrated
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