Withdrawn by the publisher.

Affected: CleanStart: rust

Security vulnerability affects the rust package. This issue is resolved in later releases. See references for vulnerability details.

In the standard library in Rust before 1.52.0, there is an optimization for joining strings that can cause uninitialized bytes to be exposed (or the program to crash) if the borrowed string changes after its length is checked.

In the standard library in Rust before 1.50.3, there is an optimization for joining strings that can cause uninitialized bytes to be exposed (or the program to crash) if the borrowed string changes after its length is checked.

Affected: openEuler:20.03-LTS-SP1: rust

Rust is a systems programming language that runs blazingly fast, prevents segfaults, and guarantees thread safety. Security Fix(es): In the standard library in Rust before 1.49.0, String::retain() function has a panic safety problem. It allows creation of a non-UTF-8 Rust string when the provided closure panics. This bug could result in a memory safety violation when other string APIs assume that UTF-8 encoding is used on the same string.(CVE-2020-36317) In the standard library in Rust before 1.50.0, read_to_end() does not validate the return value from Read in an unsafe context. This bug could lead to a buffer overflow.(CVE-2021-28875) In the standard library in Rust before 1.52.0, the Zip implementation calls __iterator_get_unchecked() more than once for the same index (under certain conditions) when next_back() and next() are used together. This bug could lead to a memory safety violation due to an unmet safety requirement for the TrustedRandomAccess trait.(CVE-2021-28878) In the standard library in Rust before 1.51.0, the Zip implementation calls __iterator_get_unchecked() for the same index more than once when nested. This bug can lead to a memory safety violation due to an unmet safety requirement for the TrustedRandomAccess trait.(CVE-2021-28877) In the standard library in Rust before 1.52.0, the Zip implementation has a panic safety issue. It calls __iterator_get_unchecked() more than once for the same index when the underlying iterator panics (in c…

rust: optimization for joining strings can cause uninitialized bytes to be exposed rust: heap-based buffer overflow in read_to_end() because it does not validate the return value from Read in an unsafe context rust: panic safety issue in Zip implementation rust: memory safety violation in Zip implementation for nested iter::Zips rust: memory safety violation in Zip implementation when next_back() and next() are used together rust: integer overflow in the Zip implementation can lead to a buffer overflow rust: double free in Vec::from_iter function if freeing the element panics

rust: optimization for joining strings can cause uninitialized bytes to be exposed rust: heap-based buffer overflow in read_to_end() because it does not validate the return value from Read in an unsafe context rust: panic safety issue in Zip implementation rust: memory safety violation in Zip implementation for nested iter::Zips rust: memory safety violation in Zip implementation when next_back() and next() are used together rust: integer overflow in the Zip implementation can lead to a buffer overflow rust: double free in Vec::from_iter function if freeing the element panics

Affected: Ubuntu:Pro:14.04:LTS: rustc, Ubuntu:Pro:16.04:LTS: rustc, Ubuntu:20.04:LTS: rustc, Ubuntu:22.04:LTS: rustc

In the standard library in Rust before 1.52.0, there is an optimization for joining strings that can cause uninitialized bytes to be exposed (or the program to crash) if the borrowed string changes after its length is checked.