![]() ![]() 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 vulnerabilities in this advisory allow performing a subset of the possible damage in a harder to track down way. Note that by design Cargo allows code execution at build time, due to build scripts and procedural macros. This would allow an attacker to corrupt one file on the machine using Cargo to extract the package. cargo-ok, it would actually replace the first two bytes of the file the symlink pointed to with ok. Then, when Cargo attempted to write "ok" into. cargo-ok symbolic link, which Cargo would extract. It was discovered that Cargo allowed packages to contain a. cargo-ok file at the root of the extracted source code once it extracted all the files. To record when an extraction is successful, Cargo writes "ok" to the. 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. 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.Ĭargo is a package manager for the rust programming language. 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. 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. We recommend users of alternate registries to excercise care in which package they download, by only including trusted dependencies in their projects. Patch files are available for Rust 1.63.0 are available in the wg-security-response repository for people building their own toolchain. 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. Rust 1.64, to be released on September 22nd, will include a fix for it. ![]() The vulnerability is present in all versions of Cargo. 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. It was discovered that Cargo did not limit the amount of data extracted from compressed archives. It is possible to gradually erode available memory to the point where named crashes for lack of resources.įdkaac commit 53fe239 was discovered to contain a floating point exception (FPE) via wav_open at /src/wav_reader.c.Ĭargo is a package manager for the rust programming language. It is possible to gradually erode available memory to the point where named crashes for lack of resources.īy spoofing the target resolver with responses that have a malformed ECDSA signature, an attacker can trigger a small memory leak. XPDF commit ffaf11c was discovered to contain a floating point exception (FPE) via DCTStream::decodeImage() at /xpdf/.īy spoofing the target resolver with responses that have a malformed EdDSA signature, an attacker can trigger a small memory leak. In Zoo Management System v1.0, there is an arbitrary file upload vulnerability in the picture upload point of the "gallery" file of the "Gallery" module in the background management system. ![]()
0 Comments
Leave a Reply. |