# RUSTSEC-2021-0059: `aesni` has been merged into the `aes` crate

> The aesni crate is deprecated and merged into aes; users should migrate to the aes crate for continued support and security.

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

## What is RUSTSEC-2021-0059?

RUSTSEC-2021-0059 is a vulnerability in aesni, published on 29 Apr 2021. 

### Official description

Please use the `aes` crate going forward. The new repository location is at:

<https://github.com/RustCrypto/block-ciphers/tree/master/aes>

AES-NI is now autodetected at runtime on `i686`/`x86-64` platforms.
If AES-NI is not present, the `aes` crate will fallback to a constant-time
portable software implementation.

To prevent this fallback (and have absence of AES-NI result in an illegal
instruction crash instead), continue to pass the same RUSTFLAGS which were
previously required for the `aesni` crate to compile:

```
RUSTFLAGS=-Ctarget-feature=+aes,+ssse3
```

## Which versions are affected by RUSTSEC-2021-0059?

1 open source package ship an affected version, including aesni.


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

## How do I fix RUSTSEC-2021-0059?

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

## Is RUSTSEC-2021-0059 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for RUSTSEC-2021-0059 and fix it if it is affected.

What it is: RUSTSEC-2021-0059 is a vulnerability in aesni, published on 29 Apr 2021. 
Exploitation: There is no known exploitation of RUSTSEC-2021-0059 in the wild and no public exploit code.

Affected packages and fixed versions:
- aesni (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-2021-0059/ (Markdown: https://insights.sbomify.com/RUSTSEC-2021-0059/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/RUSTSEC-2021-0059

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