]> git.ipfire.org Git - thirdparty/openembedded/openembedded-core-contrib.git/commit
python3: update CVE product
authorPeter Marko <peter.marko@siemens.com>
Wed, 9 Jul 2025 18:52:31 +0000 (20:52 +0200)
committerSteve Sakoman <steve@sakoman.com>
Fri, 11 Jul 2025 16:55:25 +0000 (09:55 -0700)
commit8659e3537facbf3f5f5a5080137be4d9faf9c970
tree2d3f608c367e15891397af078ce77062ba769b84
parentdb607024fdf95a03d7e08d728a6fdb6537835eee
python3: update CVE product

There are two "new" CVEs reported for python3, their CPEs are:
* CVE-2020-1171: cpe:2.3:a:microsoft:python:*:*:*:*:*:visual_studio_code:*:* (< 2020.5.0)
* CVE-2020-1192: cpe:2.3:a:microsoft:python:*:*:*:*:*:visual_studio_code:*:* (< 2020.5.0)
These are for "Visual Studio Code Python extension".

Solve this by addding CVE vendor to python CVE product to avoid
confusion with Microsoft as vendor.

Examining CVE DB for historical python entries shows:
sqlite> select vendor, product, count(*) from products where product = 'python' or product = 'cpython'
   ...> or product like 'python%3' group by vendor, product;
microsoft|python|2
python|python|1054
python_software_foundation|python|2

Note that this already shows that cpython product is not used, so
CVE-2023-33595 mentioned in 62598e1138f21a16d8b1cdd1cfe902aeed854c5c
was updated.
But let's keep it for future in case new CVE starts with that again.

Signed-off-by: Peter Marko <peter.marko@siemens.com>
Signed-off-by: Steve Sakoman <steve@sakoman.com>
meta/recipes-devtools/python/python3_3.13.4.bb