OMGeeky/advisory-db
1
0
Fork 0
mirror of https://github.com/OMGeeky/advisory-db.git synced 2025-12-29 15:56:07 +01:00
Code Issues Packages Projects Releases Wiki Activity
Files
00a4c19a4608a5010260bf3bf8e7b1e53e008bf2
advisory-db/crates/rustsec-example-crate/RUSTSEC-2019-0024.md
Tony Arcieri ac125ee29a Translate database into V3 advisory format (#420) 
As proposed in #240 and tracked in #414, this PR translates all
advisories into the new "V3" advisory format, which is based on Markdown
with leading TOML front matter.

This format makes it easier to see rendered Markdown syntax
descriptions, whether rendered by an IDE or GitHub. This should help
with both crafting advisories initially as well as review, and ideally
encourages more lengthy descriptions.

Support for this format shipped in `cargo-audit` v0.12.0 on
May 6th, 2020.
2020-10-01 18:29:11 -07:00

990 B
Raw Blame History 

[advisory]
id = "RUSTSEC-2019-0024"
package = "rustsec-example-crate"
date = "2019-10-08"
url = "https://github.com/RustSec/advisory-db/issues/158"

[versions]
patched = [">= 1.0.0"]

Test advisory with associated example crate

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 two releases:

  • 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)