sqlite3: set CVE_STATUS for CVE-2023-36191
PATCH 1/1 sqlite3: set CVE_STATUS for CVE-2023-36191
From: Changqing Li <[email protected]>
The error is a bug. It has been fixed upstream. But it is not a vulnerability. You may safely ignore the CVE.
Refer:
[1] https://www.sqlite.org/forum/forumpost/19f55ef73b
--- meta/recipes-support/sqlite/sqlite3_3.42.0.bb | 2 ++ 1 file changed, 2 insertions(+)
meta/recipes-support/sqlite/sqlite3_3.42.0.bb +2 -0
@@ -6,3 +6,5 @@ LIC_FILES_CHKSUM = "file://sqlite3.h;endline=11;md5=786d3dc581eff03f4fd9e4a77ed0 SRC_URI = "http://www.sqlite.org/2023/sqlite-autoconf-${SQLITE_PV}.tar.gz" SRC_URI[sha256sum] = "7abcfd161c6e2742ca5c6c0895d1f853c940f203304a0b49da4e1eca5d088ca6" +CVE_STATUS[CVE-2023-36191] = "The error is a bug. It has been fixed upstream. But it is not a vulnerability" +
Signature · 1 line
2.25.1
-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Changqing Li via lists.openembedded.org
Sent: Friday, September 1, 2023 11:02
To: [email protected]
Subject: [OE-core] [PATCH] sqlite3: set CVE_STATUS for CVE-2023-36191
Quoted 17 lines
From: Changqing Li <[email protected]>
The error is a bug. It has been fixed upstream. But it is not a vulnerability. You may safely ignore the CVE.
Refer:
[1] https://www.sqlite.org/forum/forumpost/19f55ef73bSigned-off-by Changqing Li <[email protected]>--- meta/recipes-support/sqlite/sqlite3_3.42.0.bb | 2 ++ 1 file changed, 2 insertions(+)meta/recipes-support/sqlite/sqlite3_3.42.0.bb +0
-0
meta/recipes-support/sqlite/sqlite3_3.42.0.bb LIC_FILES_CHKSUM = "file://sqlite3.h;endline=11;md5=786d3dc581eff03f4fd9e4a77ed0 · line 9
Quoted 4 lines
meta/recipes-support/sqlite/sqlite3_3.42.0.bb +1
-0@@ -6,3 +6,5 @@ LIC_FILES_CHKSUM = "file://sqlite3.h;endline=11;md5=786d3dc581eff03f4fd9e4a77ed0 SRC_URI = "http://www.sqlite.org/2023/sqlite-autoconf-${SQLITE_PV}.tar.gz" SRC_URI[sha256sum] = "7abcfd161c6e2742ca5c6c0895d1f853c940f203304a0b49da4e1eca5d088ca6" +CVE_STATUS[CVE-2023-36191] = "The error is a bug. It has been fixed upstream. But it is not a vulnerability"
This is wrong format since it's missing CVE status map prefix.
It needs to be something like:
CVE_STATUS[CVE-2023-36191] = "disputed: The error is a bug. It has been fixed upstream. But it is not a vulnerability"
Also since this CVE is reported in NVD DB for 3.40.1 only, this CVE exclusion is not needed for 3.42.0 recipe.
Quoted 3 lines
meta/recipes-support/sqlite/sqlite3_3.42.0.bb +1
-1+ --2.25.1
Quoted 29 lines · Peter
CAUTION: This email comes from a non Wind River email account!
Do not click links or open attachments unless you recognize the sender and know the content is safe.-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Changqing Li via lists.openembedded.org
Sent: Friday, September 1, 2023 11:02
To: [email protected]
Subject: [OE-core] [PATCH] sqlite3: setCVE_STATUSfor CVE-2023-36191Quoted 20 lines
From: Changqing Li <[email protected]>
The error is a bug. It has been fixed upstream. But it is not a vulnerability. You may safely ignore the CVE.
Refer:
[1] https://www.sqlite.org/forum/forumpost/19f55ef73bSigned-off-by Changqing Li <[email protected]>--- meta/recipes-support/sqlite/sqlite3_3.42.0.bb | 2 ++ 1 file changed, 2 insertions(+)meta/recipes-support/sqlite/sqlite3_3.42.0.bb +0
-0@@ -6,3 +6,5 @@ LIC_FILES_CHKSUM = "file://sqlite3.h;endline=11;md5=786d3dc581eff03f4fd9e4a77ed0 SRC_URI = "http://www.sqlite.org/2023/sqlite-autoconf-${SQLITE_PV}.tar.gz" SRC_URI[sha256sum] = "7abcfd161c6e2742ca5c6c0895d1f853c940f203304a0b49da4e1eca5d088ca6"
Quoted 4 lines
meta/recipes-support/sqlite/sqlite3_3.42.0.bb LIC_FILES_CHKSUM = "file://sqlite3.h;endline=11;md5=786d3dc581eff03f4fd9e4a77ed0 · line 9
Quoted 1 line
meta/recipes-support/sqlite/sqlite3_3.42.0.bb +1
-0+CVE_STATUS[CVE-2023-36191] = "The error is a bug. It has been fixed upstream. But it is not a vulnerability"This is wrong format since it's missing CVE status map prefix.
It needs to be something like:
CVE_STATUS[CVE-2023-36191] = "disputed: The error is a bug. It has been fixed upstream. But it is not a vulnerability"
Thanks for pointing out this.
Quoted 2 lines
Also since this CVE is reported in NVD DB for 3.40.1 only, this CVE exclusion is not needed for 3.42.0 recipe.
NVD DB is not 100% correct. The problematic code also exist in 3.42.0, if this is an real CVE, it will also influence 3.42.0.
So I will send an V2 with fix of above comments. we can drop this setting after the sqlite3 is upgrade to the version with
the bug fix.
Regards
Changqing
Quoted 4 lines
Quoted 4 lines
meta/recipes-support/sqlite/sqlite3_3.42.0.bb +1
-1+ --2.25.1