The remote Fedora 36 host has a package installed that is affected by a vulnerability as referenced in the FEDORA-2023-575fcaf4bf advisory.

    Security fix for CVE-2022-46176: Cargo did not perform SSH host key verification when cloning indexes and     dependencies via SSH. For more details, see the upstream [security advisory](https://blog.rust-     lang.org/2023/01/10/cve-2022-46176.html).


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 remote Fedora 37 host has a package installed that is affected by a vulnerability as referenced in the FEDORA-2023-19bcafe341 advisory.

    Security fix for CVE-2022-46176: Cargo did not perform SSH host key verification when cloning indexes and     dependencies via SSH. For more details, see the upstream [security advisory](https://blog.rust-     lang.org/2023/01/10/cve-2022-46176.html).


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.

It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2023-2023-109 advisory.

  - Cargo is a package manager for the rust programming language. After a package is downloaded, Cargo     extracts its source code in the ~/.cargo folder on disk, making it available to the Rust projects it     builds. To record when an extraction is successful, Cargo writes ok to the .cargo-ok file at the root of     the extracted source code once it extracted all the files. It was discovered that Cargo allowed packages     to contain a .cargo-ok symbolic link, which Cargo would extract. Then, when Cargo attempted to write ok     into .cargo-ok, it would actually replace the first two bytes of the file the symlink pointed to with ok.
    This would allow an attacker to corrupt one file on the machine using Cargo to extract the package. Note     that by design Cargo allows code execution at build time, due to build scripts and procedural macros. The     vulnerabilities in this advisory allow performing a subset of the possible damage in a harder to track     down way. Your dependencies must still be trusted if you want to be protected from attacks, as it's     possible to perform the same attacks with build scripts and procedural macros. The vulnerability is     present in all versions of Cargo. Rust 1.64, to be released on September 22nd, will include a fix for it.
    Since the vulnerability is just a more limited way to accomplish what a malicious build scripts or     procedural macros can do, we decided not to publish Rust point releases backporting the security fix.
    Patch files are available for Rust 1.63.0 are available in the wg-security-response repository for people     building their own toolchain. Mitigations We recommend users of alternate registries to 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 implemented server-side checks to reject these kinds of     packages years ago, and there are no packages on crates.io exploiting these vulnerabilities. crates.io     users still need to exercise care in choosing their dependencies though, as remote code execution is     allowed by design there as well. (CVE-2022-36113)

  - Cargo is a package manager for the rust programming language. It was discovered that Cargo did not limit     the amount of data extracted from compressed archives. An attacker could upload to an alternate registry a     specially crafted package that extracts way more data than its size (also known as a zip bomb),     exhausting the disk space on the machine using Cargo to download the package. Note that by design Cargo     allows code execution at build time, due to build scripts and procedural macros. The vulnerabilities in     this advisory allow performing a subset of the possible damage in a harder to track down way. Your     dependencies must still be trusted if you want to be protected from attacks, as it's possible to perform     the same attacks with build scripts and procedural macros. The vulnerability is present in all versions of     Cargo. Rust 1.64, to be released on September 22nd, will include a fix for it. Since the vulnerability is     just a more limited way to accomplish what a malicious build scripts or procedural macros can do, we     decided not to publish Rust point releases backporting the security fix. Patch files are available for     Rust 1.63.0 are available in the wg-security-response repository for people building their own toolchain.
    We recommend users of alternate registries to excercise 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     implemented server-side checks to reject these kinds of packages years ago, 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 the same concerns about build scripts and procedural macros apply here.
    (CVE-2022-36114)

  - Cargo is a Rust package manager. The Rust Security Response WG was notified that Cargo did not perform SSH     host key verification when cloning indexes and dependencies via SSH. An attacker could exploit this to     perform man-in-the-middle (MITM) attacks. This vulnerability has been assigned CVE-2022-46176. All Rust     versions containing Cargo before 1.66.1 are vulnerable. Note that even if you don't explicitly use SSH for     alternate registry indexes or crate dependencies, you might be affected by this vulnerability if you have     configured git to replace HTTPS connections to GitHub with SSH (through git's [`url.<base>.insteadOf`][1]     setting), as that'd cause you to clone the crates.io index through SSH. Rust 1.66.1 will ensure Cargo     checks the SSH host key and abort the connection if the server's public key is not already trusted. We     recommend everyone to upgrade as soon as possible. (CVE-2022-46176)

Note that Nessus has not tested for these issues 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:0133-1 advisory.

  - Cargo is a Rust package manager. The Rust Security Response WG was notified that Cargo did not perform SSH     host key verification when cloning indexes and dependencies via SSH. An attacker could exploit this to     perform man-in-the-middle (MITM) attacks. This vulnerability has been assigned CVE-2022-46176. All Rust     versions containing Cargo before 1.66.1 are vulnerable. Note that even if you don't explicitly use SSH for     alternate registry indexes or crate dependencies, you might be affected by this vulnerability if you have     configured git to replace HTTPS connections to GitHub with SSH (through git's [`url.<base>.insteadOf`][1]     setting), as that'd cause you to clone the crates.io index through SSH. Rust 1.66.1 will ensure Cargo     checks the SSH host key and abort the connection if the server's public key is not already trusted. We     recommend everyone to upgrade as soon as possible. (CVE-2022-46176)

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 ALAS2022-2023-278 advisory.

  - Cargo is a Rust package manager. The Rust Security Response WG was notified that Cargo did not perform SSH     host key verification when cloning indexes and dependencies via SSH. An attacker could exploit this to     perform man-in-the-middle (MITM) attacks. This vulnerability has been assigned CVE-2022-46176. All Rust     versions containing Cargo before 1.66.1 are vulnerable. Note that even if you don't explicitly use SSH for     alternate registry indexes or crate dependencies, you might be affected by this vulnerability if you have     configured git to replace HTTPS connections to GitHub with SSH (through git's [`url.<base>.insteadOf`][1]     setting), as that'd cause you to clone the crates.io index through SSH. Rust 1.66.1 will ensure Cargo     checks the SSH host key and abort the connection if the server's public key is not already trusted. We     recommend everyone to upgrade as soon as possible. (CVE-2022-46176)

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

An update of the rust package has been released.

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:0132-1 advisory.

  - Cargo is a Rust package manager. The Rust Security Response WG was notified that Cargo did not perform SSH     host key verification when cloning indexes and dependencies via SSH. An attacker could exploit this to     perform man-in-the-middle (MITM) attacks. This vulnerability has been assigned CVE-2022-46176. All Rust     versions containing Cargo before 1.66.1 are vulnerable. Note that even if you don't explicitly use SSH for     alternate registry indexes or crate dependencies, you might be affected by this vulnerability if you have     configured git to replace HTTPS connections to GitHub with SSH (through git's [`url.<base>.insteadOf`][1]     setting), as that'd cause you to clone the crates.io index through SSH. Rust 1.66.1 will ensure Cargo     checks the SSH host key and abort the connection if the server's public key is not already trusted. We     recommend everyone to upgrade as soon as possible. (CVE-2022-46176)

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

The remote host is affected by the vulnerability described in GLSA-202409-07 (Rust: Multiple Vulnerabilities)

    Multiple vulnerabilities have been discovered in Rust. Please review the CVE identifiers referenced below     for details.

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

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

ID	Name	Product	Family	Published	Updated	Severity
170238	Fedora 36 : rust (2023-575fcaf4bf)	Nessus	Fedora Local Security Checks	1/21/2023	11/14/2024	medium
194646	Fedora 37 : rust (2023-19bcafe341)	Nessus	Fedora Local Security Checks	4/29/2024	11/14/2024	medium
173151	Amazon Linux 2023 : cargo, clippy, rust (ALAS2023-2023-109)	Nessus	Amazon Linux Local Security Checks	3/21/2023	2/19/2024	high
170614	SUSE SLED15 / SLES15 / openSUSE 15 Security Update : rust1.65 (SUSE-SU-2023:0133-1)	Nessus	SuSE Local Security Checks	1/25/2023	7/13/2023	medium
170595	Amazon Linux 2022 : (ALAS2022-2023-278)	Nessus	Amazon Linux Local Security Checks	1/25/2023	1/25/2023	medium
204278	Photon OS 5.0: Rust PHSA-2023-5.0-0067	Nessus	PhotonOS Local Security Checks	7/24/2024	7/24/2024	medium
170608	SUSE SLED15 / SLES15 / openSUSE 15 Security Update : rust1.66 (SUSE-SU-2023:0132-1)	Nessus	SuSE Local Security Checks	1/25/2023	7/13/2023	medium
207573	GLSA-202409-07 : Rust: Multiple Vulnerabilities	Nessus	Gentoo Local Security Checks	9/22/2024	9/22/2024	high

Detections

Analytics

Plugins Search

medium

medium

high

medium

medium

medium

medium

high