Логотип exploitDog
Консоль
Логотип exploitDog

exploitDog

debian логотип

CVE-2020-36317

Опубликовано: 11 апр. 2021
Источник: debian

Описание

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.

Пакеты

ПакетСтатусВерсия исправленияРелизТип
rustcfixed1.53.0+dfsg1-1package
rustcno-dsabullseyepackage
rustcno-dsabusterpackage
rustcno-dsastretchpackage

Примечания

  • https://github.com/rust-lang/rust/issues/78498

  • https://github.com/rust-lang/rust/pull/78499

Связанные уязвимости

CVSS3: 7.5
ubuntu
почти 5 лет назад

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.

CVSS3: 5.3
redhat
больше 5 лет назад

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.

CVSS3: 7.5
nvd
почти 5 лет назад

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.

CVSS3: 7.5
msrc
почти 5 лет назад

Описание отсутствует

CVSS3: 7.5
github
больше 3 лет назад

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.