RUSTSEC-2024-0432

Dashboard / Vulnerabilities / RUSTSEC-2024-0432

RUSTSEC-2024-0432

Summary: Malicious plugin names, recipients, or identities can cause arbitrary binary execution

Details: A plugin name containing a path separator may allow an attacker to execute an arbitrary binary. Such a plugin name can be provided to the `rage` CLI through an attacker-controlled recipient or identity string, or an attacker-controlled plugin name via the `-j` flag. On UNIX systems, a directory matching `age-plugin-*` needs to exist in the working directory for the attack to succeed. The binary is executed with a single flag, either `--age-plugin=recipient-v1` or `--age-plugin=identity-v1`. The standard input includes the recipient or identity string, and the random file key (if encrypting) or the header of the file (if decrypting). The format is constrained by the [age-plugin](https://c2sp.org/age-plugin) protocol. An equivalent issue was fixed in [the reference Go implementation of age](https://github.com/FiloSottile/age), see advisory [GHSA-32gq-x56h-299c](https://github.com/FiloSottile/age/security/advisories/GHSA-32gq-x56h-299c). Thanks to ⬡-49016 for reporting this issue.

References: https://crates.io/crates/rage, https://rustsec.org/advisories/RUSTSEC-2024-0432.html, https://github.com/str4d/rage/commit/703152ecfa86f27952a35b57dd525ed39396a227