From: Peter Korsgaard <peter@korsgaard.com>
To: Bernd Kuhls <bernd.kuhls@t-online.de>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Asaf Kahlon <asafka7@gmail.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/python3: security bump version to 3.11.4
Date: Thu, 06 Jul 2023 11:24:59 +0200 [thread overview]
Message-ID: <87h6qh4ck4.fsf@48ers.dk> (raw)
In-Reply-To: <87v8flf150.fsf@48ers.dk> (Peter Korsgaard's message of "Sun, 18 Jun 2023 13:41:47 +0200")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
>>>>> "Bernd" == Bernd Kuhls <bernd.kuhls@t-online.de> writes:
>> Rebased two patches.
>> Changelog:
>> https://docs.python.org/release/3.11.4/whatsnew/changelog.html#python-3-11-4
>> Fixes the following security problems:
>> - gh-99889: Fixed a security in flaw in uu.decode() that could allow for
>> directory traversal based on the input if no out_file was specified.
>> - gh-104049: Do not expose the local on-disk location in directory
>> indexes produced by http.client.SimpleHTTPRequestHandler.
>> - gh-102153: urllib.parse.urlsplit() now strips leading C0 control and
>> space characters following the specification for URLs defined by WHATWG
>> in response to CVE-2023-24329. Patch by Illia Volochii.
>> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> Committed, thanks.
Committed to 2023.02.x and 2023.05.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-07-06 9:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 16:53 [Buildroot] [PATCH 1/1] package/python3: security bump version to 3.11.4 Bernd Kuhls
2023-06-18 11:41 ` Peter Korsgaard
2023-07-06 9:24 ` Peter Korsgaard [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=87h6qh4ck4.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=asafka7@gmail.com \
--cc=bernd.kuhls@t-online.de \
--cc=buildroot@buildroot.org \
--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