From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: nvd@nist.gov
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] CVE-2021-4034 version range fix
Date: Fri, 8 Sep 2023 22:59:55 +0200 [thread overview]
Message-ID: <20230908225955.176edc80@windsurf> (raw)
In-Reply-To: <20230902193434.4865dbd4@windsurf>
Hello NVD maintainers,
Gentle ping on the below bug report. Thanks!
Thomas Petazzoni
On Sat, 2 Sep 2023 19:34:34 +0200
Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> Dear NVD maintainers,
>
> CVE-2021-4034 is marked in the NVD database as affecting all versions
> of the polkit project due to the following "Configuration 1":
>
> cpe:2.3:a:polkit_project:polkit:*:*:*:*:*:*:*:*
>
> However, as indicated in
> https://nvd.nist.gov/vuln/detail/CVE-2021-4034, this issue has been
> fixed in the upstream polkit project as of commit
> https://gitlab.freedesktop.org/polkit/polkit/-/commit/a2bf5c9c83b6ae46cbd5c779d3055bff81ded683.
>
> In turn, this commit is integrated in polkit since version 121:
>
> polkit$ git tag --contains a2bf5c9c83b6ae46cbd5c779d3055bff81ded683
> 121
> 122
> 123
>
> So, the "Configuration 1" should be fixed to indicate that only
> versions < 121 are affected. Could this be addressed in your NVD
> database?
>
> Best regards,
>
> Thomas Petazzoni
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-09-08 21:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-02 17:34 [Buildroot] CVE-2021-4034 version range fix Thomas Petazzoni via buildroot
2023-09-08 20:59 ` Thomas Petazzoni via buildroot [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230908225955.176edc80@windsurf \
--to=buildroot@buildroot.org \
--cc=nvd@nist.gov \
--cc=thomas.petazzoni@bootlin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox