RUSTSEC-2021-0061 json
`aes-ctr` 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>
The `aes` crate now has an optional `ctr` feature which autodetects SIMD features on `i686`/`x86-64` targets and uses them if available, or otherwise falls back to the implementation in the `ctr` crate.
If you would prefer not to have this autodetection performed, use the `aes` crate directly with the `ctr` crate.
Patch / fix
- github.com/RustCrypto/block-ciphers#200 pull request
Is RUSTSEC-2021-0061 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-ctr | >=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.