Поиск уязвимостей
Количество 9
Количество 9
CVE-2023-40030
Cargo downloads a Rust project’s dependencies and compiles the project. Starting in Rust 1.60.0 and prior to 1.72, Cargo did not escape Cargo feature names when including them in the report generated by `cargo build --timings`. A malicious package included as a dependency may inject nearly arbitrary HTML here, potentially leading to cross-site scripting if the report is subsequently uploaded somewhere. The vulnerability affects users relying on dependencies from git, local paths, or alternative registries. Users who solely depend on crates.io are unaffected. Rust 1.60.0 introduced `cargo build --timings`, which produces a report of how long the different steps of the build process took. It includes lists of Cargo features for each crate. Prior to Rust 1.72, Cargo feature names were allowed to contain almost any characters (with some exceptions as used by the feature syntax), but it would produce a future incompatibility warning about them since Rust 1.49. crates.io is far more str...
CVE-2023-40030
Cargo downloads a Rust project’s dependencies and compiles the project. Starting in Rust 1.60.0 and prior to 1.72, Cargo did not escape Cargo feature names when including them in the report generated by `cargo build --timings`. A malicious package included as a dependency may inject nearly arbitrary HTML here, potentially leading to cross-site scripting if the report is subsequently uploaded somewhere. The vulnerability affects users relying on dependencies from git, local paths, or alternative registries. Users who solely depend on crates.io are unaffected. Rust 1.60.0 introduced `cargo build --timings`, which produces a report of how long the different steps of the build process took. It includes lists of Cargo features for each crate. Prior to Rust 1.72, Cargo feature names were allowed to contain almost any characters (with some exceptions as used by the feature syntax), but it would produce a future incompatibility warning about them since Rust 1.49. crates.io is far more strin
CVE-2023-40030
Malicious dependencies can inject arbitrary JavaScript into cargo-generated timing reports
CVE-2023-40030
Cargo downloads a Rust project\u2019s dependencies and compiles the pr ...
SUSE-SU-2023:3722-1
Security update for rust, rust1.72
ROS-20240729-11
Уязвимость rust
GHSA-wrrj-h57r-vx9p
Malicious dependencies can inject arbitrary JavaScript into cargo-generated timing reports
ALT-PU-2023-8783
ALT-PU-2023-8783: package `rust` update to version 1.72.0-alt1
ALT-PU-2023-6236
ALT-PU-2023-6236: package `rust` update to version 1.72.1-alt0.p10.1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2023-40030 Cargo downloads a Rust project’s dependencies and compiles the project. Starting in Rust 1.60.0 and prior to 1.72, Cargo did not escape Cargo feature names when including them in the report generated by `cargo build --timings`. A malicious package included as a dependency may inject nearly arbitrary HTML here, potentially leading to cross-site scripting if the report is subsequently uploaded somewhere. The vulnerability affects users relying on dependencies from git, local paths, or alternative registries. Users who solely depend on crates.io are unaffected. Rust 1.60.0 introduced `cargo build --timings`, which produces a report of how long the different steps of the build process took. It includes lists of Cargo features for each crate. Prior to Rust 1.72, Cargo feature names were allowed to contain almost any characters (with some exceptions as used by the feature syntax), but it would produce a future incompatibility warning about them since Rust 1.49. crates.io is far more str... | CVSS3: 6.1 | 1% Низкий | около 3 лет назад | |
CVE-2023-40030 Cargo downloads a Rust project’s dependencies and compiles the project. Starting in Rust 1.60.0 and prior to 1.72, Cargo did not escape Cargo feature names when including them in the report generated by `cargo build --timings`. A malicious package included as a dependency may inject nearly arbitrary HTML here, potentially leading to cross-site scripting if the report is subsequently uploaded somewhere. The vulnerability affects users relying on dependencies from git, local paths, or alternative registries. Users who solely depend on crates.io are unaffected. Rust 1.60.0 introduced `cargo build --timings`, which produces a report of how long the different steps of the build process took. It includes lists of Cargo features for each crate. Prior to Rust 1.72, Cargo feature names were allowed to contain almost any characters (with some exceptions as used by the feature syntax), but it would produce a future incompatibility warning about them since Rust 1.49. crates.io is far more strin | CVSS3: 6.1 | 1% Низкий | около 3 лет назад | |
CVE-2023-40030 Malicious dependencies can inject arbitrary JavaScript into cargo-generated timing reports | CVSS3: 6.1 | 1% Низкий | 9 месяцев назад | |
CVE-2023-40030 Cargo downloads a Rust project\u2019s dependencies and compiles the pr ... | CVSS3: 6.1 | 1% Низкий | около 3 лет назад | |
SUSE-SU-2023:3722-1 Security update for rust, rust1.72 | 1% Низкий | около 3 лет назад | ||
ROS-20240729-11 Уязвимость rust | CVSS3: 6.1 | 1% Низкий | больше 2 лет назад | |
GHSA-wrrj-h57r-vx9p Malicious dependencies can inject arbitrary JavaScript into cargo-generated timing reports | 1% Низкий | около 3 лет назад | ||
ALT-PU-2023-8783 ALT-PU-2023-8783: package `rust` update to version 1.72.0-alt1 | CVSS3: 6.1 | 1% Низкий | около 3 лет назад | |
ALT-PU-2023-6236 ALT-PU-2023-6236: package `rust` update to version 1.72.1-alt0.p10.1 | CVSS3: 6.1 | 1% Низкий | около 3 лет назад |
Уязвимостей на страницу