Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: nvd <nvd@nist.gov>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: [Buildroot] CVE-2024-6232 version range fix
Date: Tue, 31 Dec 2024 12:02:35 +0100	[thread overview]
Message-ID: <20241231120235.30949440@windsurf> (raw)

Dear NVD maintainers,

CVE-2024-6232 reported against Python is documented at
https://nvd.nist.gov/vuln/detail/CVE-2024-6232 as affecting
all versions of Python prior to 3.12.5.

However, the fix for this issue has been backported to maintained
versions of Python, which means some versions numerically before 3.12.5
are NOT affected.

Namely:

* https://github.com/python/cpython/commit/d449caf8a179e3b954268b3a88eb9170be3c8fbf
  is the fix that was backported to the 3.11.x branch of Python, and is
  part of Python 3.11.10, so every version 3.11.x >= 3.11.10 are not affected.

* https://github.com/python/cpython/commit/743acbe872485dc18df4d8ab2dc7895187f062c4
  is the fix that was backported to the 3.10.x branch of Python, and is
  part of Python 3.10.15, so every version 3.10.x >= 3.10.15 are not
  affected.

Would it be possible to adjust the CVE entry accordingly?

Thanks a lot!

Thomas
-- 
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-12-31 11:02 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=20241231120235.30949440@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