- 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
This is a test advisory useful for verifying RustSec tooling and vulnerability detection pipelines are working correctly. Aside from the fact that it is filed against an example crate, it is otherwise considered by the Advisory Database itself to be a normal security advisory.
It's filed against `rustsec-example-crate`, an otherwise completely empty crate with no functionality or code, which has three releases:
- [v0.0.0] - *unaffected* by this advisory (but *yanked* from crates.io) - [v0.0.1] - *vulnerable* according to this advisory - [v1.0.0] - *patched* by this advisory
[v0.0.0]: https://crates.io/crates/rustsec-example-crate/0.0.0 [v0.0.1]: https://crates.io/crates/rustsec-example-crate/0.0.1 [v1.0.0]: https://crates.io/crates/rustsec-example-crate/1.0.0
Patch / fix
- crates.io rustsec-example-crate 1.0.0
Is RUSTSEC-2019-0024 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 | rustsec-example-crate | >=0.0.1, <1.0.0 |
1.0.0 |
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.