GHSA-4fg7-vxc8-qx5w rage vulnerable to malicious plugin names, recipients, or identities causing arbitrary binary execution

• crates.io rage: >= 0.6.0, < 0.6.1 → fixed in 0.6.1 • crates.io age: >= 0.6.0, < 0.6.1 → fixed in 0.6.1 • crates.io age: >= 0.7.0, < 0.7.2 → fixed in 0.7.2 • crates.io age: >= 0.8.0, < 0.8.2 → fixed in 0.8.2 • crates.io age: >= 0.9.0, < 0.9.3 → fixed in 0.9.3 • crates.io age: >= 0.10.0, < 0.10.1 → fixed in 0.10.1 • crates.io age: >= 0.11.0, < 0.11.1 → fixed in 0.11.1 • crates.io rage: >= 0.7.0, < 0.7.2 → fixed in 0.7.2 • crates.io rage: >= 0.8.0, < 0.8.2 → fixed in 0.8.2 • crates.io rage: >= 0.9.0, < 0.9.3 → fixed in 0.9.3 • crates.io rage: >= 0.10.0, < 0.10.1 → fixed in 0.10.1 • crates.io rage: >= 0.11.0, < 0.11.1 → fixed in 0.11.1

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 to the following `age` APIs when the `plugin` feature flag is enabled: • `age::plugin::Identity::from_str` (or equivalently `str::parse::()`) • `age::plugin::Identity::default_for_plugin` • `age::plugin::IdentityPluginV1::new` • `age::plugin::Recipient::from_str` (or equivalently `str::parse::()`) • `age::plugin::RecipientPluginV1::new` 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 protocol. An equivalent issue was fixed in the reference Go implementation of age, see advisory GHSA-32gq-x56h-299c. Thanks to ⬡-49016 for reporting this issue.