- Sometimes, the difference in the codebase of the fixed CVE's version and the current version of the package is huge. - This would make the backporting of the CVE not a feasible option. - And due to other dependencies and limitations, the upgrade of the package might not be possible as well. - This commit would allow users to add a description via CVE_STATUS and still show the CVE as vulnerable.
Signed-off-by: Dhairya Nagodra <[email protected]> --- meta/conf/cve-check-map.conf | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta/conf/cve-check-map.conf b/meta/conf/cve-check-map.conf index 17b0f15571..b9df41a6f3 100644 --- a/meta/conf/cve-check-map.conf +++ b/meta/conf/cve-check-map.conf @@ -13,6 +13,8 @@ CVE_CHECK_STATUSMAP[fixed-version] = "Patched" CVE_CHECK_STATUSMAP[unpatched] = "Unpatched" # use when CVE is confirmed by upstream but fix is still not available CVE_CHECK_STATUSMAP[vulnerable-investigating] = "Unpatched" +# use when CVE fix is not compatible to the current version and cannot be backported. +CVE_CHECK_STATUSMAP[cannot-backport] = "Unpatched" # used for migration from old concept, do not use for new vulnerabilities CVE_CHECK_STATUSMAP[ignored] = "Ignored"
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#202424): https://lists.openembedded.org/g/openembedded-core/message/202424 Mute This Topic: https://lists.openembedded.org/mt/107518622/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
