aboutsummaryrefslogtreecommitdiffstats
path: root/meta/recipes-core/glibc/glibc/CVE-2019-9169.patch
diff options
context:
space:
mode:
authorRoss Burton <ross.burton@intel.com>2019-12-08 20:35:57 +0200
committerArmin Kuster <akuster808@gmail.com>2019-12-10 07:37:28 -0800
commitb52d6340acdad27d41caf057b78f181297a9a75e (patch)
tree1561773b7fa0a92b7042b3fc190da849ffa7db38 /meta/recipes-core/glibc/glibc/CVE-2019-9169.patch
parent1f3863bc31e03207856f55591cbf17543e188587 (diff)
downloadopenembedded-core-b52d6340acdad27d41caf057b78f181297a9a75e.tar.gz
cve-check: fetch CVE data once at a time instead of in a single call
This code used to construct a single SQL statement that fetched the NVD data for every CVE requested. For recipes such as the kernel where there are over 2000 CVEs to report this can hit the variable count limit and the query fails with "sqlite3.OperationalError: too many SQL variables". The default limit is 999 variables, but some distributions such as Debian set the default to 250000. As the NVD table has an index on the ID column, whilst requesting the data CVE-by-CVE is five times slower when working with 2000 CVEs the absolute time different is insignificant: 0.05s verses 0.01s on my machine. (From OE-Core rev: 53d0cc1e9b7190fa66d7ff1c59518f91b0128d99) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Armin Kuster <akuster808@gmail.com>
Diffstat (limited to 'meta/recipes-core/glibc/glibc/CVE-2019-9169.patch')
0 files changed, 0 insertions, 0 deletions