Skip to content
Discussion options

You must be logged in to vote

Yes, the missing NVD applicability data explains the NVD/CPE matching path here. The
authoritative NVD API record
currently has vulnStatus: "Awaiting Analysis" and no configurations containing affected CPE matches.
That is different from an analyzed record saying your component is unaffected.

Dependency-Track's known-vulnerability analysis documentation
says its NVD matching uses CPEs and the CPE name-matching rules. A version appearing in the CVE's prose
description does not provide the missing structured CPE applicability information. Your valid component
CPE alone cannot supply the other side of that match.

The absence of a PURL also matters when comparing results from other scanners: …

Replies: 1 comment 4 replies

Comment options

You must be logged in to vote
4 replies
@smarbecker
Comment options

@Drako01
Comment options

@smarbecker
Comment options

@smarbecker
Comment options

Answer selected by smarbecker
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants