]> code.ossystems Code Review - openembedded-core.git/commit
cve-check: rewrite look to fix false negatives
authorRoss Burton <ross.burton@intel.com>
Sun, 24 Nov 2019 23:50:13 +0000 (15:50 -0800)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Mon, 25 Nov 2019 21:37:01 +0000 (21:37 +0000)
commit0f42a1d4dbb74ab39e81449cf222302bcc04f7db
tree6b201e4402050c23bd01492603971911b9181b43
parent15f6b4b59805db40df4eff6d5a2809f6f05b66c1
cve-check: rewrite look to fix false negatives

A previous optimisation was premature and resulted in false-negatives in the report.

Rewrite the checking algorithm to first get the list of potential CVEs by
vendor:product, then iterate through every matching CPE for that CVE to
determine if the bounds match or not.  By doing this in two stages we can know
if we've checked every CPE, instead of accidentally breaking out of the scan too
early.

(From OE-Core rev: d61aff9e22704ad69df1f7ab0f8784f4e7cc0c69)

Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
meta/classes/cve-check.bbclass