Bug 13109

Summary: Implement CPE to package to Release mapping
Product: [Yocto Project Subprojects] Security Response Tool Reporter: David Reyna <david.reyna>
Component: GeneralAssignee: David Reyna <david.reyna>
Status: RESOLVED WONTFIX QA Contact:
Severity: enhancement    
Priority: Medium+ CC: randy.macleod, ross.burton
Version: 2.7   
Target Milestone: 5.0 M4   
Hardware: x86   
OS: Multiple   
Whiteboard: NIR 11/03
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Yes (doc changes required)

Description David Reyna 2018-12-29 09:36:49 UTC
The CPE Goal:
1)	Match CVEs to Releases
2)	Match CVEs to Builds

The CPE Problem:
1) CVEs
	* May be missing CPEs (e.g. all new CVEs)
	* May be missing YP matches (false negatives)
	* May have errors (false positives)

2) YP Recipes
	* No existing CPE map list
	* Recipe naming does not fully match package naming
	* Package version numbers may not exactly match

Proposed CPE Solution:
1) Allow for SRT-based CPEs to fill in the matching gaps
2) Create a "Package" object that can map NIST-CPEs to YP-CPEs
3) Start maintaining a Recipe-To-Package table
4) Allow for flexible name/version mapping [any|version(s)], with confidence levels
Comment 1 David Reyna 2020-09-24 03:42:40 UTC
We have been working on an implementation, and it will be ready for YP-3.3
Comment 2 David Reyna 2020-12-16 07:30:48 UTC
It turns out that this is very very hard, give the poor mapping of CPEs to recipes, even when CPEs are avialable.

My new strategy is to find ways to integrate with existing second and third tools in an agnostic manner.
Comment 3 David Reyna 2023-10-18 20:48:03 UTC
Perhaps data from CVE Checker can help provide advice on how to proceed.

Wind River's solution is that our triage management identifies the recipe from the CVE (mostly form the description given that the CPE table is usually empty for new CVEs), and our defect system tracks the CVEs by those recipe names. 

Ideally we have at least semi-automated assistance in those mappings.

David
Comment 4 David Reyna 2023-11-09 18:48:39 UTC
I am moving this away from "NEEDINFO". 

While this feature request definity needs more information about systemic difficulties in finding a resolution, it does not need the urgency of NEEDINFO.
Comment 5 David Reyna 2024-05-09 16:59:36 UTC
This needs a mandate to implement. Will re-file new defect when that happens.