From e3e689775499a6ce8179e7cb1ec887cc22bda180 Mon Sep 17 00:00:00 2001 From: "Sergey \"Shnatsel\" Davidoff" Date: Sat, 5 Nov 2022 18:45:24 +0100 Subject: [PATCH] Update RUSTSEC-2019-0024.md (#1464) --- crates/rustsec-example-crate/RUSTSEC-2019-0024.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/crates/rustsec-example-crate/RUSTSEC-2019-0024.md b/crates/rustsec-example-crate/RUSTSEC-2019-0024.md index 390d642..c5e4038 100644 --- a/crates/rustsec-example-crate/RUSTSEC-2019-0024.md +++ b/crates/rustsec-example-crate/RUSTSEC-2019-0024.md @@ -7,6 +7,7 @@ url = "https://github.com/RustSec/advisory-db/issues/158" [versions] patched = [">= 1.0.0"] +unaffected = ["< 0.0.1"] ``` # Test advisory with associated example crate @@ -17,13 +18,12 @@ 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 two releases: +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 -(Technically there is a third release, v0.0.0, which is yanked, but otherwise -identical to the v0.0.1 release) - +[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