RUSTSEC-2021-0060 json
`aes-soft` has been merged into the `aes` crate
published 5y ago modified 5y ago
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
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 force the use of a constant-time portable implementation on these platforms, even if AES-NI is available, use the new `force-soft` feature of the `aes` crate to disable autodetection.
Patch / fix
- github.com/RustCrypto/block-ciphers#200 pull request
Is RUSTSEC-2021-0060 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | aes-soft | >=0.0.0-0 |
no fix listed |
References
Sources
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.