* [PATCH v2] python3-pytest: add CVE_PRODUCT
@ 2024-03-20 16:09 Emil Kronborg
2024-03-21 12:13 ` [OE-core] " Richard Purdie
2024-03-21 17:10 ` Ross Burton
0 siblings, 2 replies; 5+ messages in thread
From: Emil Kronborg @ 2024-03-20 16:09 UTC (permalink / raw)
To: openembedded-core; +Cc: rasmus.villemoes, Emil Kronborg
For some reason, the CVE product is just called py and not pytest in the
NIST NVD database. Since the database only accept keywords with at least
3 characters, the CVE vendor must also be specified.
Signed-off-by: Emil Kronborg <emil.kronborg@protonmail.com>
---
Changes in v2:
- I forgot to sign the first version.
meta/recipes-devtools/python/python3-pytest_8.0.2.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/recipes-devtools/python/python3-pytest_8.0.2.bb b/meta/recipes-devtools/python/python3-pytest_8.0.2.bb
index 57e979e909c3..080b89ebdd5e 100644
--- a/meta/recipes-devtools/python/python3-pytest_8.0.2.bb
+++ b/meta/recipes-devtools/python/python3-pytest_8.0.2.bb
@@ -5,6 +5,8 @@ DESCRIPTION = "The pytest framework makes it easy to write small tests, yet scal
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://LICENSE;md5=bd27e41b6550fe0fc45356d1d81ee37c"
+CVE_PRODUCT = "pytest:py"
+
SRC_URI[sha256sum] = "d4051d623a2e0b7e51960ba963193b09ce6daeb9759a451844a21e4ddedfc1bd"
DEPENDS += "python3-setuptools-scm-native"
--
2.44.0
^ permalink raw reply related [flat|nested] 5+ messages in thread
* Re: [OE-core] [PATCH v2] python3-pytest: add CVE_PRODUCT
2024-03-20 16:09 [PATCH v2] python3-pytest: add CVE_PRODUCT Emil Kronborg
@ 2024-03-21 12:13 ` Richard Purdie
2024-03-23 16:06 ` Emil Kronborg
2024-03-21 17:10 ` Ross Burton
1 sibling, 1 reply; 5+ messages in thread
From: Richard Purdie @ 2024-03-21 12:13 UTC (permalink / raw)
To: emil.kronborg, openembedded-core; +Cc: rasmus.villemoes
On Wed, 2024-03-20 at 16:09 +0000, Emil Kronborg via
lists.openembedded.org wrote:
> For some reason, the CVE product is just called py and not pytest in
> the
> NIST NVD database. Since the database only accept keywords with at
> least
> 3 characters, the CVE vendor must also be specified.
>
> Signed-off-by: Emil Kronborg <emil.kronborg@protonmail.com>
> ---
> Changes in v2:
> - I forgot to sign the first version.
>
> meta/recipes-devtools/python/python3-pytest_8.0.2.bb | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/meta/recipes-devtools/python/python3-pytest_8.0.2.bb
> b/meta/recipes-devtools/python/python3-pytest_8.0.2.bb
> index 57e979e909c3..080b89ebdd5e 100644
> --- a/meta/recipes-devtools/python/python3-pytest_8.0.2.bb
> +++ b/meta/recipes-devtools/python/python3-pytest_8.0.2.bb
> @@ -5,6 +5,8 @@ DESCRIPTION = "The pytest framework makes it easy to
> write small tests, yet scal
> LICENSE = "MIT"
> LIC_FILES_CHKSUM =
> "file://LICENSE;md5=bd27e41b6550fe0fc45356d1d81ee37c"
>
> +CVE_PRODUCT = "pytest:py"
> +
> SRC_URI[sha256sum] =
> "d4051d623a2e0b7e51960ba963193b09ce6daeb9759a451844a21e4ddedfc1bd"
>
> DEPENDS += "python3-setuptools-scm-native"
I worry this is a misfiled CPE rather than general statement that
they'd always use this for pytest CVEs. We might want to talk to them
about tweaking it to be consistent? I'm certainly unsure about taking
this patch as it might mask future issues?
Cheers,
Richard
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [OE-core] [PATCH v2] python3-pytest: add CVE_PRODUCT
2024-03-20 16:09 [PATCH v2] python3-pytest: add CVE_PRODUCT Emil Kronborg
2024-03-21 12:13 ` [OE-core] " Richard Purdie
@ 2024-03-21 17:10 ` Ross Burton
2024-03-23 16:09 ` Emil Kronborg
1 sibling, 1 reply; 5+ messages in thread
From: Ross Burton @ 2024-03-21 17:10 UTC (permalink / raw)
To: emil.kronborg@protonmail.com; +Cc: OE-core, rasmus.villemoes@prevas.dk
On 20 Mar 2024, at 16:09, Emil Kronborg via lists.openembedded.org <emil.kronborg=protonmail.com@lists.openembedded.org> wrote:
>
> For some reason, the CVE product is just called py and not pytest in the
> NIST NVD database. Since the database only accept keywords with at least
> 3 characters, the CVE vendor must also be specified.
I can only find two CVEs with the CPE pytest:py and either of them are actually related to the pytest package:
https://nvd.nist.gov/vuln/detail/CVE-2020-29651
https://nvd.nist.gov/vuln/detail/CVE-2022-42969
These issues relate to https://github.com/pytest-dev/py which is not pytest.
Ross
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [OE-core] [PATCH v2] python3-pytest: add CVE_PRODUCT
2024-03-21 12:13 ` [OE-core] " Richard Purdie
@ 2024-03-23 16:06 ` Emil Kronborg
0 siblings, 0 replies; 5+ messages in thread
From: Emil Kronborg @ 2024-03-23 16:06 UTC (permalink / raw)
To: Richard Purdie; +Cc: openembedded-core, rasmus.villemoes
On Thu, Mar 21, 2024 at 12:13 +0000, Richard Purdie wrote:
> I worry this is a misfiled CPE rather than general statement that
> they'd always use this for pytest CVEs. We might want to talk to them
> about tweaking it to be consistent? I'm certainly unsure about taking
> this patch as it might mask future issues?
I made a mistake. This CPE belongs to the py project by pytest [1]. The
vendor name being http://pytest.org tricked me. Searching for pytest in
the NIST NVD database yields a single CPE: pytest:py, so I think it is
fine to keep it as is, even though a CPE might appear as pytest:pytest
instead of python:pytest.
[1]: https://github.com/pytest-dev/py
--
Emil Kronborg
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [OE-core] [PATCH v2] python3-pytest: add CVE_PRODUCT
2024-03-21 17:10 ` Ross Burton
@ 2024-03-23 16:09 ` Emil Kronborg
0 siblings, 0 replies; 5+ messages in thread
From: Emil Kronborg @ 2024-03-23 16:09 UTC (permalink / raw)
To: Ross Burton; +Cc: OE-core, rasmus.villemoes@prevas.dk
On Thu, Mar 21, 2024 at 17:10 +0000, Ross Burton wrote:
> I can only find two CVEs with the CPE pytest:py and either of them are actually related to the pytest package:
>
> https://nvd.nist.gov/vuln/detail/CVE-2020-29651
> https://nvd.nist.gov/vuln/detail/CVE-2022-42969
>
> These issues relate to https://github.com/pytest-dev/py which is not pytest.
You are right. This patch should not be pulled.
--
Emil Kronborg
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2024-03-23 16:09 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-03-20 16:09 [PATCH v2] python3-pytest: add CVE_PRODUCT Emil Kronborg
2024-03-21 12:13 ` [OE-core] " Richard Purdie
2024-03-23 16:06 ` Emil Kronborg
2024-03-21 17:10 ` Ross Burton
2024-03-23 16:09 ` Emil Kronborg
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).