Undefined behavior via premature vector initialization
Published Apr 1, 2021 · Updated Aug 3, 2024
Memory-safety error in the telemetry crate through 0.1.2 causes undefined behavior when misc::vec_with_size receives a panicking Clone. The function sets the vector length before initializing its elements, so unwinding from value.clone() would drop uninitialized entries. RustSec withdrew the advisory because public functions instantiate this private generic function only with primitive Clone types, whose clone operations cannot panic, so safe dependent code cannot trigger the behavior.
Summary
What happened
Memory-safety error in the telemetry crate through 0.1.2 causes undefined behavior when misc::vec_with_size receives a panicking Clone. The function sets the vector length before initializing its elements, so unwinding from value.clone() would drop uninitialized entries. RustSec withdrew the advisory because public functions instantiate this private generic function only with primitive Clone types, whose clone operations cannot panic, so safe dependent code cannot trigger the behavior.
The record
- CVE
- CVE-2021-29937
- Published
- Apr 1, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-908
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Apr 1, 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.
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