From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Titouan Christophe via buildroot <buildroot@buildroot.org>
Cc: Titouan Christophe <titouan.christophe@mind.be>,
James Hilliard <james.hilliard1@gmail.com>,
thomas.perale@mind.be
Subject: Re: [Buildroot] [PATCH] package/python-tornado: bump to version 6.5
Date: Fri, 30 May 2025 21:52:00 +0200 [thread overview]
Message-ID: <20250530215200.23ef4e06@windsurf> (raw)
In-Reply-To: <20250519145126.4114666-1-titouan.christophe@mind.be>
On Mon, 19 May 2025 16:51:26 +0200
Titouan Christophe via buildroot <buildroot@buildroot.org> wrote:
> Among other things, this fixes the following CVE:
> - CVE-2025-47287: When Tornado's ``multipart/form-data`` parser encounters
> certain errors, it logs a warning but continues trying to
> parse the remainder of the data. This allows remote
> attackers to generate an extremely high volume of logs,
> constituting a DoS attack.
>
> Read the full changelog:
> https://github.com/tornadoweb/tornado/releases/tag/v6.5.0
>
> Signed-off-by: Titouan Christophe <titouan.christophe@mind.be>
> ---
> package/python-tornado/python-tornado.hash | 4 ++--
> package/python-tornado/python-tornado.mk | 4 ++--
> 2 files changed, 4 insertions(+), 4 deletions(-)
Applied to next after cherry-picking the commit from master adding the
security fix, and making sure it gets dropped as part of the version
bump. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2025-05-30 19:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-19 14:51 [Buildroot] [PATCH] package/python-tornado: bump to version 6.5 Titouan Christophe via buildroot
2025-05-30 19:52 ` 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=20250530215200.23ef4e06@windsurf \
--to=buildroot@buildroot.org \
--cc=james.hilliard1@gmail.com \
--cc=thomas.perale@mind.be \
--cc=thomas.petazzoni@bootlin.com \
--cc=titouan.christophe@mind.be \
/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