OMGeeky/advisory-db
1
0
Fork 0
mirror of https://github.com/OMGeeky/advisory-db.git synced 2025-12-27 06:29:31 +01:00
Code Issues Packages Projects Releases Wiki Activity

Correct typo and URL (#491)

Browse Source 
Distributed Weakness filing went dark last year
Instead use, the official pages at mitre corp.

Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>
This commit is contained in:
Philippe Ombredanne
2020-11-21 17:03:50 +01:00
committed by GitHub
parent cd034f750b
commit f5505edb82
2 changed files with 3 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
CONTRIBUTING.md
View File

@@ -18,7 +18,8 @@ this repository containing the new advisory:
Feel free to do either or both of these as you see fit (we recommend you do both):
4. [Yank] the affected versions of the crate.
5. Request a CVE for your vulnerability: https://iwantacve.org/
5. Request a CVE for your vulnerability. See for details:
https://cve.mitre.org/cve/request_id.html and https://cveform.mitre.org .
Alternatively, you can create a GitHub Security Advisory (GHSA) and let them request
a CVE for you. In this case, you can add the GHSA ID to the RustSec advisory via the
`aliases` field.

2
README.md
View File

@@ -29,7 +29,7 @@ See [CONTRIBUTING.md] for more information.
See [EXAMPLE_ADVISORY.md] for a template.
Advisories are formatted in [Markdown] with [TOML] "front matter".
Below is the scehma of the "front matter" section of an advisory:
Below is the schema of the "front matter" section of an advisory:
```toml
# Before you submit a PR using this template, **please delete the comments**