diff options
| author | Peter Marko <peter.marko@siemens.com> | 2024-11-24 21:13:42 +0100 |
|---|---|---|
| committer | Steve Sakoman <steve@sakoman.com> | 2025-02-12 06:29:33 -0800 |
| commit | 2d4aee3d97bdcdd48ccb2a4fd34399e13cca9e22 (patch) | |
| tree | 10be5133250806cffe02a112896f2b5022ed1ab0 /meta/recipes-devtools/python/python3/0001-Avoid-shebang-overflow-on-python-config.py.patch | |
| parent | a1b7ded85a1e4791038ff69115635c01f36b4a74 (diff) | |
| download | poky-2d4aee3d97bdcdd48ccb2a4fd34399e13cca9e22.tar.gz | |
cve-check: fix cvesInRecord
Currently flag cvesInRecord is set to false if all CVEs are ignored or
patched. This is inconsistent as it shows false if a CVE was fixed via
patch and true if this CVE was fixed by upgrade. In both cases the CVE
is valid and was fixed.
As I understand this flag, it should say if any CVE exists for
particular component's product (regardless of how this CVE is handled)
and can be used to validate if a product is correctly set.
Note that skipping ignored CVEs may make sense in some cases, as ignored
may mean that NVD DB is wrong, but in many cases it is ignored for other
reasons. Further patch can be done to evaluate ignore subtype but that
would be against my understanding of this flag as described above.
(From OE-Core rev: 0fb2bfb8d6c77009385d7deca2e758bdee5c9b07)
Signed-off-by: Peter Marko <peter.marko@siemens.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
(cherry picked from commit c5d499693672ec9619392011b765941cf94aa319)
Signed-off-by: Steve Sakoman <steve@sakoman.com>
Diffstat (limited to 'meta/recipes-devtools/python/python3/0001-Avoid-shebang-overflow-on-python-config.py.patch')
0 files changed, 0 insertions, 0 deletions