<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/meta/classes/cve-check.bbclass, branch uninative-2.6</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=uninative-2.6</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=uninative-2.6'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2019-06-20T12:14:21+00:00</updated>
<entry>
<title>cve-check: Consider CVE that affects versions with less than operator</title>
<updated>2019-06-20T12:14:21+00:00</updated>
<author>
<name>Pierre Le Magourou</name>
<email>pierre.lemagourou@softbankrobotics.com</email>
</author>
<published>2019-06-19T13:59:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=9562ec9c361d6f036317b614e196b1fefe8d867b'/>
<id>urn:sha1:9562ec9c361d6f036317b614e196b1fefe8d867b</id>
<content type='text'>
In the NVD json CVE feed, affected versions can be strictly matched to a
version, but they can also be matched with the operator '&lt;='.

Add a new condition in the sqlite query to match affected versions that
are defined with the operator '&lt;='. Then use LooseVersion to discard all
versions that are not relevant.

(From OE-Core rev: 3bf63bc60848d91e90c23f6d854d22b78832aa2d)

Signed-off-by: Pierre Le Magourou &lt;pierre.lemagourou@softbankrobotics.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>cve-check: Manage CVE_PRODUCT with more than one name</title>
<updated>2019-06-20T12:14:21+00:00</updated>
<author>
<name>Pierre Le Magourou</name>
<email>pierre.lemagourou@softbankrobotics.com</email>
</author>
<published>2019-06-19T13:59:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=95f0d11e21ad476efb4b46c87a8c94730d7c355f'/>
<id>urn:sha1:95f0d11e21ad476efb4b46c87a8c94730d7c355f</id>
<content type='text'>
In some rare cases (eg. curl recipe) the CVE_PRODUCT contains more than
one name.

(From OE-Core rev: 7f62a20b32a3d42f04ec58786a7d0db68ef1bb05)

Signed-off-by: Pierre Le Magourou &lt;pierre.lemagourou@softbankrobotics.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>cve-check: Remove dependency to cve-check-tool-native</title>
<updated>2019-06-20T12:14:21+00:00</updated>
<author>
<name>Pierre Le Magourou</name>
<email>pierre.lemagourou@softbankrobotics.com</email>
</author>
<published>2019-06-19T13:59:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=05fb9db63372d32e6ab3cb56186d7bcb09e26b43'/>
<id>urn:sha1:05fb9db63372d32e6ab3cb56186d7bcb09e26b43</id>
<content type='text'>
Use the new update-cve-db recipe to update database.

(From OE-Core rev: bc144b028f6f51252f4359248f6921028bcb6780)

Signed-off-by: Pierre Le Magourou &lt;pierre.lemagourou@softbankrobotics.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>cve-check: Allow multiple entries in CVE_PRODUCT</title>
<updated>2018-10-29T17:01:45+00:00</updated>
<author>
<name>Grygorii Tertychnyi</name>
<email>gtertych@cisco.com</email>
</author>
<published>2018-10-29T15:13:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=e93457c1511037a9ebac8e9794db65d9ff0113f4'/>
<id>urn:sha1:e93457c1511037a9ebac8e9794db65d9ff0113f4</id>
<content type='text'>
There are both "curl" and "libcurl" CPEs in NVD.
All "curl" CVEs are currently missing in the reports.

Hence, switch "CVE_PRODUCT" to a space separated list.
It is useful for recipes generating several packages,
that have different product names in NVD.

(From OE-Core rev: 404f75e026393ddc55da87f6f04fb1201cff4e11)

Signed-off-by: Grygorii Tertychnyi &lt;gtertych@cisco.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>cve-check.bbclass: do not download the CVE DB in package-specific tasks</title>
<updated>2018-08-15T20:45:58+00:00</updated>
<author>
<name>Konstantin Shemyak</name>
<email>konstantin.shemyak@ge.com</email>
</author>
<published>2018-08-13T07:23:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=f7e24cc377b00f2341cd3168bbd0201828547255'/>
<id>urn:sha1:f7e24cc377b00f2341cd3168bbd0201828547255</id>
<content type='text'>
Disable downloading of the vulnerability DB in do_check_cves() task.

When invoked in this task, cve-check-tool attempts re-download of the CVE DB
if the latter is older than certain threshold. While reasonable for a
stand-alone CVE checker, this behavior can cause errors in parallel builds
if the build time is longer than this threshold:
* Other tasks might be using the DB.
* Several packages can start the download of the same file at the same time.

This check is not really needed, as the DB has been downloaded by
cve_check_tool:do_populate_cve_db() which is a prerequisite of any do_build().
The DB will be at most (threshold + build_time) old.

(From OE-Core rev: 125789b6ee6d47ab84192230f63971c4e22418ba)

Signed-off-by: Konstantin Shemyak &lt;konstantin.shemyak@ge.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>cve-check.bbclass: detect CVE IDs listed on multiple lines</title>
<updated>2018-05-15T09:56:49+00:00</updated>
<author>
<name>Jon Szymaniak</name>
<email>jon.szymaniak.foss@gmail.com</email>
</author>
<published>2018-05-09T21:45:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=dd5bf3e4d2ad66d8572d622a147cea1a8fddb40d'/>
<id>urn:sha1:dd5bf3e4d2ad66d8572d622a147cea1a8fddb40d</id>
<content type='text'>
Some backported patches fix multiple CVEs and list the corresponding
identifiers on multiple lines, rather than on a single line.

cve-check.bbclass yields false positive warnings when CVE IDs are
presented on multiple lines because re.search() returns only
the first match.

An example of this behavior may be found when running do_cve_check() on
the wpa-supplicant recipe while in the rocko branch. Only CVE-2017-13077
is reported to be patched by commit de57fd8, despite the patch including
fixes for a total of 9 CVEs.

This is resolved by iterating over all regular expression matches,
rather than just the first.

(From OE-Core rev: 8fb70ce2df66fc8404395ecbe66a75d0038f22dd)

Signed-off-by: Jon Szymaniak &lt;jon.szymaniak.foss@gmail.com&gt;
Signed-off-by: Ross Burton &lt;ross.burton@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>cve-check-tool: correctly exported web proxies</title>
<updated>2018-02-24T10:31:46+00:00</updated>
<author>
<name>Konstantin Shemyak</name>
<email>konstantin.shemyak@ge.com</email>
</author>
<published>2018-02-19T14:35:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=2e07b1c0bb6e88cd0338b477ab9e69b1fe605e6c'/>
<id>urn:sha1:2e07b1c0bb6e88cd0338b477ab9e69b1fe605e6c</id>
<content type='text'>
The binary 'cve-check-update' downloads the CVE database from the Internet.
If the system is behind a web proxy, the download fails, as proxy-related
variables are not exported.
In turn, 'cve-check-tool' does not connect to the network and correspondingly
does not need exported proxies.

Exported all proxy-related environment variables to 'cve-check-update' and
removed the unneeded export from 'cve-check-tool'.

(From OE-Core rev: 17db210975c740aff12732c511cf4fb32b507365)

Signed-off-by: Konstantin Shemyak &lt;konstantin.shemyak@ge.com&gt;
Signed-off-by: Ross Burton &lt;ross.burton@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>cve-check: short-circuit checking if CVE_PRODUCT isn't set</title>
<updated>2018-02-16T18:05:40+00:00</updated>
<author>
<name>Ross Burton</name>
<email>ross.burton@intel.com</email>
</author>
<published>2018-02-09T12:43:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=325096cd2a801b6e1a741be8deaf272e9b5f3f37'/>
<id>urn:sha1:325096cd2a801b6e1a741be8deaf272e9b5f3f37</id>
<content type='text'>
For some recipes is is meaningless to do a CVE check, for example packagegroups
or images.  Check that CVE_PRODUCT is set and short-circuit the scan if it
isn't.

(From OE-Core rev: d1e7cb5c9e0d5d253b6bb5c968fa58944ea42d06)

Signed-off-by: Ross Burton &lt;ross.burton@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>cve-check: allow recipes to override their version</title>
<updated>2018-02-16T18:05:40+00:00</updated>
<author>
<name>Ross Burton</name>
<email>ross.burton@intel.com</email>
</author>
<published>2018-02-09T12:37:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=4873716c0cb436c82e877db2bba2d748b675c08b'/>
<id>urn:sha1:4873716c0cb436c82e877db2bba2d748b675c08b</id>
<content type='text'>
For reasons which I don't understand, the Berkeley DB tarball is version 5.3.28
but in CVE reports the version is 11.2.5.3.28.

To handle this allow recipes to override their version as well as their name.

(From OE-Core rev: 36fbf96cf284acbc810ff3bf00702f1f82bc0da9)

Signed-off-by: Ross Burton &lt;ross.burton@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>cve-check: put log in T so it doesn't get deleted by rm_work</title>
<updated>2018-02-16T18:05:40+00:00</updated>
<author>
<name>Ross Burton</name>
<email>ross.burton@intel.com</email>
</author>
<published>2018-02-08T22:14:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=ccd664d8d0afb03a66f00804b919b9878962eea5'/>
<id>urn:sha1:ccd664d8d0afb03a66f00804b919b9878962eea5</id>
<content type='text'>
This is where the other task logs go, so it's a sensible place to put it.

(From OE-Core rev: 4bbb8cd5f3943231ab5be0448d1b0d4a08341249)

Signed-off-by: Ross Burton &lt;ross.burton@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
</feed>
