CVE-2018-25023: High severity Servo Smallvec Rust vulnerability
Affected versions of this crate called mem::uninitialized() to create values of a user-supplied type T. This is unsound e.g. if T is a reference type (which must be non-null and thus may not remain uninitialized). The flaw was corrected by avoiding the use of mem::uninitialized(), using MaybeUninit instead.
Other sources
An issue was discovered in the smallvec crate before 0.6.13 for Rust. It can create an uninitialized value of any type, including a reference type.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
rust/smallvecto a version that resolves this vulnerability.Fixed in 0.6.13 - Upgrade
Upgrade
smallvecto a version that resolves this vulnerability.Fixed in 0.6.13
Event History
Frequently Asked Questions
What is the severity of CVE-2018-25023?
CVE-2018-25023 is considered a serious vulnerability due to potential undefined behavior when using uninitialized memory.
How do I fix CVE-2018-25023?
To fix CVE-2018-25023, update your version of the smallvec crate to 0.6.13 or later, which replaces the use of mem::uninitialized() with MaybeUninit.
Which versions of smallvec are affected by CVE-2018-25023?
Versions of smallvec prior to 0.6.13 are affected by CVE-2018-25023.
What kind of vulnerabilities does CVE-2018-25023 expose?
CVE-2018-25023 exposes vulnerabilities related to the use of uninitialized references, potentially leading to unsafe memory usage.
Is CVE-2018-25023 related to Rust's memory safety?
Yes, CVE-2018-25023 directly impacts Rust's memory safety guarantees due to improper handling of uninitialized memory.