---
id: RUSTSEC-2024-0432
aliases:
  - GHSA-4fg7-vxc8-qx5w
  - RUSTSEC-2024-0433
title: >-
  Malicious plugin names, recipients, or identities can cause arbitrary binary
  execution
summary: >-
  Malicious plugin names, recipients, or identities can cause arbitrary binary
  execution
severity: none
vendor: rage
product: rage
ecosystem: rust
affected:
  - 'rage >= 0.11.0, < 0.11.1'
patched:
  - rage 0.11.1
published: '2024-12-18'
updated: '2026-10-12'
sourceUpdated: '2026-10-12T18:00:02.665971455Z'
source: OSV
sourceUrl: 'https://osv.dev/vulnerability/RUSTSEC-2024-0432'
references:
  - url: 'https://crates.io/crates/rage'
  - url: 'https://rustsec.org/advisories/RUSTSEC-2024-0432.html'
  - url: >-
      https://github.com/str4d/rage/commit/703152ecfa86f27952a35b57dd525ed39396a227
tags:
  - osv
  - rust
ingestedAt: '2026-10-13T11:45:30.172Z'
---

## Overview

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.

## Affected packages

- `rage >= 0.11.0, < 0.11.1`

## Remediation

Upgrade to a patched release:

- `rage 0.11.1`