# RUSTSEC-2024-0333: `rsa-export` is unmaintained

> The unmaintained rsa-export crate uses non-constant-time operations, potentially exposing RSA keys to side-channel attacks.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Apr 2024

## What is RUSTSEC-2024-0333?

RUSTSEC-2024-0333 is a vulnerability in rsa-export, published on 6 Apr 2024. 

### Official description

This crate has been deprecated in favour of using the native support for exporting RSA keys into the standard PEM format.  
See [docs.rs documentation].

In addition to that, the operations in this crate (arithmetic and Base64 encoding) are not done in constant-time, 
potentially [exposing the user to sidechannel attacks].

[docs.rs documentation]: https://docs.rs/rsa/0.9.6/rsa/index.html#pkcs8-rsa-key-encoding
[exposing the user to sidechannel attacks]: https://arxiv.org/pdf/2108.04600.pdf

## Which versions are affected by RUSTSEC-2024-0333?

1 open source package ship an affected version, including rsa-export.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rsa-export` | crates.io | From 0.0.0-0 | None |

## How do I fix RUSTSEC-2024-0333?

No fix has been published for RUSTSEC-2024-0333 yet. Limit exposure of the affected software until one is available.

## Is RUSTSEC-2024-0333 being exploited?

There is no known exploitation of RUSTSEC-2024-0333 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for RUSTSEC-2024-0333 and fix it if it is affected.

What it is: RUSTSEC-2024-0333 is a vulnerability in rsa-export, published on 6 Apr 2024. 
Exploitation: There is no known exploitation of RUSTSEC-2024-0333 in the wild and no public exploit code.

Affected packages and fixed versions:
- rsa-export (crates.io): affected from 0.0.0-0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/RUSTSEC-2024-0333/ (Markdown: https://insights.sbomify.com/RUSTSEC-2024-0333/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/RUSTSEC-2024-0333

---
From sbomify Insights: https://insights.sbomify.com/RUSTSEC-2024-0333/
Summaries are generated and may contain mistakes; the official description above is the record.