Question 300
Which validation finding BEST demonstrates that “Validate vendor advisory applicability and build lineage for each product before prioritizing both equally.” resolved this specific concern: Two vulnerabilities share a CVE identifier across different package forks but only one fork is actually affected.
Explanation
Correct Answer
“The exposure register records affected forks separately from unaffected versions with evidence.” is direct acceptance evidence for the response “Validate vendor advisory applicability and build lineage for each product before prioritizing both equally.”. It resolves the uncertainty introduced by “Two vulnerabilities share a CVE identifier across different package forks but only one fork is actually affected.” using an observable test or record.
Incorrect Answers
This result belongs to prioritizing a reachable VPN exploit under attack over an isolated higher-CVSS lab finding, whereas the requested acceptance proof concerns checking affected package forks and vendor lineage before assigning the same CVE to all derivatives.
That observation may be true while checking affected package forks and vendor lineage before assigning the same CVE to all derivatives remains unresolved; it reflects checking whether an optional vulnerable module is enabled before accepting a CVE proof of concept.
Such an outcome relates to prioritizing public exposure of personnel records over equally misconfigured public marketing content. The question asks for evidence of checking affected package forks and vendor lineage before assigning the same CVE to all derivatives.