zlib: add vendor to CVE_PRODUCT to exclude false positives
PATCH 1/1 zlib: add vendor to CVE_PRODUCT to exclude false positives
To avoid false positives (such as CVE-2023-6992, cloudflare:zlib), add a CVE_PRODUCT to identify the vendor that has been used.
--- meta/recipes-core/zlib/zlib_1.2.13.bb | 3 +++ 1 file changed, 3 insertions(+)
meta/recipes-core/zlib/zlib_1.2.13.bb +3 -0
@@ -45,3 +45,6 @@ do_install_ptest() { } BBCLASSEXTEND = "native nativesdk" + +# adding 'CVE_PRODUCT' to avoid false detection of CVEs +CVE_PRODUCT = "zlib:zlib"
There is also gnu:zlib in CVE reports for zlib...
sqlite3 nvdcve_2-1.db
sqlite> select vendor, count(*) from products where product='zlib' group by vendor; cloudflare|1
gnu|1
zlib|13
sqlite> select * from products where product='zlib' and vendor = 'gnu'; CVE-2016-9842|gnu|zlib|1.2.3.4|>=|1.2.9|<
Peter
Quoted 30 lines
-----Original Message-----
From: [email protected] <openembedded- [email protected]> On Behalf Of Het Patel via lists.openembedded.org
Sent: Thursday, August 8, 2024 8:24
To: [email protected]
Cc: Het Patel <[email protected]>
Subject: [OE-core] [PATCH] zlib: add vendor toCVE_PRODUCTto exclude false positivesTo avoid false positives (such as CVE-2023-6992, cloudflare:zlib), add a
CVE_PRODUCTto identify the vendor that has been used.Signed-off-by Het Patel <[email protected]>--- meta/recipes-core/zlib/zlib_1.2.13.bb | 3 +++ 1 file changed, 3 insertions(+)meta/recipes- renamed from meta/recipes-core/zlib/zlib_1.2.13.bb +0
-0core/zlib/zlib_1.2.13.bb
indexec977a3035..8f3814068a100644meta/recipes-core/zlib/zlib_1.2.13.bb +3
-0@@ -45,3 +45,6 @@ do_install_ptest() { } BBCLASSEXTEND = "native nativesdk" + +# adding 'CVE_PRODUCT' to avoid false detection of CVEs +CVE_PRODUCT = "zlib:zlib"
Quoted 10 lines · Peter Marko via lists.openembedded.org
There is also gnu:zlib in CVE reports for zlib...
sqlite3 nvdcve_2-1.db
sqlite> select vendor,count(*)from products where product='zlib' group by vendor; cloudflare|1
gnu|1
zlib|13
sqlite> select * from products where product='zlib' and vendor = 'gnu'; CVE-2016-9842|gnu|zlib|1.2.3.4|>=|1.2.9|<
Which is obviously wrong, as there isn’t a GNU zlib. The references point to the same git tree, so this is a mistake in the CPE data. The CPE database acknowledges this by deprecating the gnu:zlib name and pointing at zlib:zlib:
<cpe-item name="cpe:/a:gnu:zlib:-" deprecated="true" deprecation_date="2022-06-22T16:40:44.440Z">
<title xml:lang="en-US">GNU zlib</title>
<cpe-23:cpe23-item name="cpe:2.3:a:gnu:zlib:-:*:*:*:*:*:*:*">
<cpe-23:deprecation date="2022-06-22T12:40:44.440-04:00">
<cpe-23:deprecated-by name="cpe:2.3:a:zlib:zlib:-:*:*:*:*:*:*:*" type="NAME_CORRECTION"/>
</cpe-23:deprecation>
</cpe-23:cpe23-item></cpe-item>
We _could_ canonicalise the CPEs when we load the CVEs but that’s another 500MB file to fetch, so I’m unconvinced that’s worthwhile.
I was actually going to mail NIST about any attempt at rationalising the CPE data for historical CVEs, I’ll use this as a test case to see if they’re willing to retroactively fix the name in historical CVEs.
Ross