Debian Package Tracker
Register | Log in
Subscribe

cargo

Rust package manager

Choose email to subscribe with

general
  • source: cargo (main)
  • version: 0.66.0+ds1-1
  • maintainer: Rust Maintainers (archive) (DMD)
  • uploaders: Vasudev Kamath [DMD] – Luca Bruno [DMD] – Ximin Luo [DMD] – Angus Lees [DMD]
  • arch: all any
  • std-ver: 4.2.1
  • VCS: Git (Browse)
versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]
[pool directory]
  • o-o-stable: 0.43.1-3~deb10u1
  • oldstable: 0.47.0-3
  • stable: 0.66.0+ds1-1
versioned links
  • 0.35.0-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 0.43.1-3~deb10u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 0.47.0-3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 0.66.0+ds1-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
binaries
  • cargo (3 bugs: 0, 3, 0, 0)
  • cargo-doc
package is gone
This package is not in any development repository. This probably means that the package has been removed (or has been renamed). Thus the information here is of little interest ... the package is going to disappear unless someone takes it over and reintroduces it.
action needed
Debci reports failed tests high
  • unstable: fail (log)
    The tests ran in 0:00:45
    Last run: 2024-05-16T01:44:09.000Z
    Previous status: unknown

  • testing: pass (log)
    The tests ran in 0:04:45
    Last run: 2024-05-05T00:12:03.000Z
    Previous status: unknown

  • stable: pass (log)
    The tests ran in 0:03:42
    Last run: 2025-03-25T14:37:50.000Z
    Previous status: unknown

Created: 2024-07-29 Last update: 2025-05-26 00:32
2 security issues in sid high

There are 2 open security issues in sid.

2 important issues:
  • CVE-2023-38497: Cargo downloads the Rust project’s dependencies and compiles the project. Cargo prior to version 0.72.2, bundled with Rust prior to version 1.71.1, did not respect the umask when extracting crate archives on UNIX-like systems. If the user downloaded a crate containing files writeable by any local user, another local user could exploit this to change the source code compiled and executed by the current user. To prevent existing cached extractions from being exploitable, the Cargo binary version 0.72.2 included in Rust 1.71.1 or later will purge caches generated by older Cargo versions automatically. As a workaround, configure one's system to prevent other local users from accessing the Cargo directory, usually located in `~/.cargo`.
  • 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 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.
Created: 2023-08-05 Last update: 2024-05-07 18:18
2 security issues in trixie high

There are 2 open security issues in trixie.

2 important issues:
  • CVE-2023-38497: Cargo downloads the Rust project’s dependencies and compiles the project. Cargo prior to version 0.72.2, bundled with Rust prior to version 1.71.1, did not respect the umask when extracting crate archives on UNIX-like systems. If the user downloaded a crate containing files writeable by any local user, another local user could exploit this to change the source code compiled and executed by the current user. To prevent existing cached extractions from being exploitable, the Cargo binary version 0.72.2 included in Rust 1.71.1 or later will purge caches generated by older Cargo versions automatically. As a workaround, configure one's system to prevent other local users from accessing the Cargo directory, usually located in `~/.cargo`.
  • 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 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.
Created: 2023-08-05 Last update: 2024-05-03 22:30
RFH: The maintainer is looking for help with this package. normal
The current maintainer is looking for someone who can help with the maintenance of this package. If you are interested in this package, please consider helping out. One way you can help is offer to be a co-maintainer or triage bugs in the BTS. Please see bug number #860116 for more information.
Created: 2017-12-02 Last update: 2017-12-02 00:25
No known security issue in bookworm wishlist

There are 2 open security issues in bookworm.

2 ignored issues:
  • CVE-2023-38497: Cargo downloads the Rust project’s dependencies and compiles the project. Cargo prior to version 0.72.2, bundled with Rust prior to version 1.71.1, did not respect the umask when extracting crate archives on UNIX-like systems. If the user downloaded a crate containing files writeable by any local user, another local user could exploit this to change the source code compiled and executed by the current user. To prevent existing cached extractions from being exploitable, the Cargo binary version 0.72.2 included in Rust 1.71.1 or later will purge caches generated by older Cargo versions automatically. As a workaround, configure one's system to prevent other local users from accessing the Cargo directory, usually located in `~/.cargo`.
  • 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 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.
Created: 2023-08-05 Last update: 2025-02-27 05:02
news
[rss feed]
  • [2024-05-08] cargo REMOVED from testing (Debian testing watch)
  • [2024-05-04] cargo 0.70.1+ds1-3 MIGRATED to testing (Debian testing watch)
  • [2024-03-17] Accepted cargo 0.70.1+ds1-3 (source) into unstable (Fabian Grünbichler) (signed by: Fabian Gruenbichler)
  • [2024-03-17] Accepted cargo 0.70.1+ds1-2.1 (all armel armhf source) into unstable (Emanuele Rocca)
  • [2024-01-05] cargo 0.70.1+ds1-2 MIGRATED to testing (Debian testing watch)
  • [2023-12-30] Accepted cargo 0.70.1+ds1-2 (source) into unstable (Fabian Grünbichler) (signed by: Fabian Gruenbichler)
  • [2023-12-21] cargo 0.70.1+ds1-1 MIGRATED to testing (Debian testing watch)
  • [2023-12-16] Accepted cargo 0.70.1+ds1-1 (source) into unstable (Fabian Grünbichler) (signed by: Fabian Gruenbichler)
  • [2023-12-16] Accepted cargo 0.70.1+ds1-1~exp1 (source) into experimental (Fabian Grünbichler) (signed by: Fabian Gruenbichler)
  • [2023-12-12] cargo 0.66.0+ds2-2 MIGRATED to testing (Debian testing watch)
  • [2023-12-12] cargo 0.66.0+ds2-2 MIGRATED to testing (Debian testing watch)
  • [2023-12-04] Accepted cargo 0.66.0+ds2-2 (source) into unstable (Fabian Grünbichler) (signed by: Fabian Gruenbichler)
  • [2023-12-03] Accepted cargo 0.66.0+ds2-1 (source) into unstable (Fabian Grünbichler) (signed by: Fabian Gruenbichler)
  • [2023-11-28] Accepted cargo 0.70.1-1~exp1 (source) into experimental (Fabian Grünbichler) (signed by: Fabian Gruenbichler)
  • [2023-01-18] cargo 0.66.0+ds1-1 MIGRATED to testing (Debian testing watch)
  • [2023-01-12] Accepted cargo 0.66.0+ds1-1 (source) into unstable (Fabian Gruenbichler)
  • [2023-01-12] cargo 0.66.0-1 MIGRATED to testing (Debian testing watch)
  • [2023-01-09] Accepted cargo 0.66.0-1 (source) into unstable (Fabian Gruenbichler)
  • [2022-12-09] cargo 0.63.1-3 MIGRATED to testing (Debian testing watch)
  • [2022-12-07] Accepted cargo 0.63.1-3 (source) into unstable (Fabian Gruenbichler) (signed by: Jochen Sprickerhof)
  • [2022-11-19] Accepted cargo 0.63.1-2 (source) into unstable (Fabian Gruenbichler) (signed by: Sylvestre Ledru)
  • [2022-11-16] Accepted cargo 0.63.1-1 (source) into unstable (Fabian Gruenbichler) (signed by: Sylvestre Ledru)
  • [2022-05-06] cargo 0.57.0-7 MIGRATED to testing (Debian testing watch)
  • [2022-05-02] Accepted cargo 0.57.0-7 (source) into unstable (Peter Michael Green)
  • [2022-04-10] Accepted cargo 0.57.0-6 (source) into experimental (Peter Michael Green)
  • [2022-03-09] Accepted cargo 0.57.0-5 (source) into unstable (Ximin Luo) (signed by: infinity0@debian.org)
  • [2022-03-07] Accepted cargo 0.57.0-4 (source) into unstable (Ximin Luo) (signed by: infinity0@debian.org)
  • [2021-10-29] cargo 0.57.0-3 MIGRATED to testing (Debian testing watch)
  • [2021-10-24] Accepted cargo 0.57.0-3 (source) into unstable (Ximin Luo) (signed by: infinity0@debian.org)
  • [2021-10-24] Accepted cargo 0.57.0-2 (source) into unstable (Ximin Luo) (signed by: infinity0@debian.org)
  • 1
  • 2
bugs [bug history graph]
  • all: 2
  • RC: 0
  • I&N: 2
  • M&W: 0
  • F&P: 0
  • patch: 0
links
  • homepage
  • buildd: logs, cross
  • popcon
  • browse source code
  • edit tags
  • other distros
  • security tracker
  • screenshots
  • debci

Debian Package Tracker — Copyright 2013-2025 The Distro Tracker Developers
Report problems to the tracker.debian.org pseudo-package in the Debian BTS.
Documentation — Bugs — Git Repository — Contributing