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 stringent about what it considers a valid feature name and has not allowed such feature names. As the feature names were included unescaped in the timings report, they could be used to inject Javascript into the page, for example with a feature name like `features = ["<img src='' onerror=alert(0)"]`. If this report were subsequently uploaded to a domain that uses credentials, the injected Javascript could access resources from the website visitor. This issue was fixed in Rust 1.72 by turning the future incompatibility warning into an error. Users should still exercise care in which package they download, by only including trusted dependencies in their projects. Please note that even with these vulnerabilities fixed, by design Cargo allows arbitrary code execution at build time thanks to build scripts and procedural macros: a malicious dependency will be able to cause damage regardless of these vulnerabilities. crates.io has server-side checks preventing this attack, and there are no packages on crates.io exploiting these vulnerabilities. crates.io users still need to excercise care in choosing their dependencies though, as remote code execution is allowed by design there as well.

An update of the rust package has been released.

The remote Fedora 40 host has packages installed that are affected by a vulnerability as referenced in the FEDORA-2023-6f419dc91b advisory.

    - Update cargo-c to version 0.7.29+cargo-0.74.0.
    - Update the cargo crate to version 0.74.0.
    - Update cbindgen to version 0.26.0.
    - Add a compat package version 0.24 of the bindgen crate.
    - Update the crates-io crate to version 0.38.0.
    - Update the git2-curl crate to version 0.18.0.
    - Initial packaging of the cargo-credential and cargo-credential-libsecret crates.


Tenable has extracted the preceding description block directly from the Fedora security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The version of rust installed on the remote host is prior to 1.68.2-1. It is, therefore, affected by a vulnerability as referenced in the ALAS2-2024-2426 advisory.

  - 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 stringent about what it     considers a valid feature name and has not allowed such feature names. As the feature names were included     unescaped in the timings report, they could be used to inject Javascript into the page, for example with a     feature name like `features = [<img src='' onerror=alert(0)]`. If this report were subsequently uploaded     to a domain that uses credentials, the injected Javascript could access resources from the website     visitor. This issue was fixed in Rust 1.72 by turning the future incompatibility warning into an error.
    Users should still exercise care in which package they download, by only including trusted dependencies in     their projects. Please note that even with these vulnerabilities fixed, by design Cargo allows arbitrary     code execution at build time thanks to build scripts and procedural macros: a malicious dependency will be     able to cause damage regardless of these vulnerabilities. crates.io has server-side checks preventing this     attack, and there are no packages on crates.io exploiting these vulnerabilities. crates.io users still     need to excercise care in choosing their dependencies though, as remote code execution is allowed by     design there as well. (CVE-2023-40030)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

It is, therefore, affected by a vulnerability as referenced in the ALAS2023-2024-497 advisory.

  - 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 stringent about what it     considers a valid feature name and has not allowed such feature names. As the feature names were included     unescaped in the timings report, they could be used to inject Javascript into the page, for example with a     feature name like `features = [<img src='' onerror=alert(0)]`. If this report were subsequently uploaded     to a domain that uses credentials, the injected Javascript could access resources from the website     visitor. This issue was fixed in Rust 1.72 by turning the future incompatibility warning into an error.
    Users should still exercise care in which package they download, by only including trusted dependencies in     their projects. Please note that even with these vulnerabilities fixed, by design Cargo allows arbitrary     code execution at build time thanks to build scripts and procedural macros: a malicious dependency will be     able to cause damage regardless of these vulnerabilities. crates.io has server-side checks preventing this     attack, and there are no packages on crates.io exploiting these vulnerabilities. crates.io users still     need to excercise care in choosing their dependencies though, as remote code execution is allowed by     design there as well. (CVE-2023-40030)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote SUSE Linux SLED15 / SLED_SAP15 / SLES15 / SLES_SAP15 / openSUSE 15 host has packages installed that are affected by a vulnerability as referenced in the SUSE-SU-2023:3722-1 advisory.

  - 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 stringent about what it     considers a valid feature name and has not allowed such feature names. As the feature names were included     unescaped in the timings report, they could be used to inject Javascript into the page, for example with a     feature name like `features = [<img src='' onerror=alert(0)]`. If this report were subsequently uploaded     to a domain that uses credentials, the injected Javascript could access resources from the website     visitor. This issue was fixed in Rust 1.72 by turning the future incompatibility warning into an error.
    Users should still exercise care in which package they download, by only including trusted dependencies in     their projects. Please note that even with these vulnerabilities fixed, by design Cargo allows arbitrary     code execution at build time thanks to build scripts and procedural macros: a malicious dependency will be     able to cause damage regardless of these vulnerabilities. crates.io has server-side checks preventing this     attack, and there are no packages on crates.io exploiting these vulnerabilities. crates.io users still     need to excercise care in choosing their dependencies though, as remote code execution is allowed by     design there as well. (CVE-2023-40030)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Severity
204317	Photon OS 5.0: Rust PHSA-2023-5.0-0177	Nessus	PhotonOS Local Security Checks	medium
194627	Fedora 40 : rust-cargo / rust-cargo-c / rust-cargo-credential / etc (2023-6f419dc91b)	Nessus	Fedora Local Security Checks	medium
189337	Amazon Linux 2 : rust (ALAS-2024-2426)	Nessus	Amazon Linux Local Security Checks	medium
189320	Amazon Linux 2023 : cargo, clippy, rust (ALAS2023-2024-497)	Nessus	Amazon Linux Local Security Checks	medium
181776	SUSE SLED15 / SLES15 / openSUSE 15 Security Update : rust, rust1.72 (SUSE-SU-2023:3722-1)	Nessus	SuSE Local Security Checks	medium

Detections

Analytics

CVE-2023-40030

medium

Tenable Plugins

medium

medium

medium

medium

medium