Skip to content

Commit 8e880fc

Browse files
committed
doc/triage.md: explain "waiting analysis"
Say that we should write a report if the NIST page says "awaiting analysis". Change-Id: Ieabecd3743b6495c679650e950a466f5846aec70 Reviewed-on: https://go-review.googlesource.com/c/vulndb/+/555895 Run-TryBot: Jonathan Amsterdam <[email protected]> TryBot-Result: Gopher Robot <[email protected]> Reviewed-by: Tatiana Bradley <[email protected]> LUCI-TryBot-Result: Go LUCI <[email protected]>
1 parent 941ecd0 commit 8e880fc

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

doc/triage.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -216,3 +216,11 @@ Commonly missing packages include:
216216

217217
- libgpgme-dev
218218
- libdevmapper-dev
219+
220+
### "awaiting analysis"
221+
222+
When the NIST page says "AWAITING ANALYSIS", write the report; don't wait for them
223+
to finish their analysis. "Awaiting analysis" just means that NVD hasn't yet looked
224+
at the vulnerability and assigned a severity score/CWE etc. Since we don't care about
225+
those pieces of information, we can ignore that banner and just create a report if
226+
the vulnerability is in scope for our database.

0 commit comments

Comments
 (0)