From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: nvd <nvd@nist.gov>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: [Buildroot] CVE-2023-0687 version range fix
Date: Tue, 6 Feb 2024 15:11:44 +0100 [thread overview]
Message-ID: <20240206151144.103d5b2b@windsurf> (raw)
Dear NVD maintainers,
Your entry at https://nvd.nist.gov/vuln/detail/CVE-2023-0687 for
CVE-2023-0687 states that the affected CPE ID is
cpe:2.3:a:gnu:glibc:2.38:*:*:*:*:*:*:*, which indicates that only glibc
2.38 is affected.
But actually, the bug was fixed in glibc 2.38, so it's all versions
prior to 2.38 that are affected. According to the bug report at
https://sourceware.org/bugzilla/show_bug.cgi?id=29444, this issue was
fixed in commit
https://sourceware.org/git/?p=glibc.git;a=commit;h=801af9fafd4689337ebf27260aa115335a0cb2bc,
and:
$ git tag --contains 801af9fafd46
glibc-2.38
glibc-2.38.9000
So the commit fixing this issue made it to the 2.38 release.
Do you think you could adjust the NVD entry for this CVE ?
Thanks a lot in advance!
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
reply other threads:[~2024-02-06 14:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240206151144.103d5b2b@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