From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Titouan Christophe <titouanchristophe@gmail.com>
Cc: Daniel Price <daniel.price@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/redis: security bump to v7.0.4
Date: Thu, 11 Aug 2022 22:25:13 +0200 [thread overview]
Message-ID: <20220811222513.7ef2b670@windsurf> (raw)
In-Reply-To: <20220811185448.1122716-1-titouanchristophe@gmail.com>
On Thu, 11 Aug 2022 20:54:48 +0200
Titouan Christophe <titouanchristophe@gmail.com> wrote:
> From the release notes:
>
> ================================================================================
> Redis 7.0.4 Released Monday Jul 18 12:00:00 IST 2022
> ================================================================================
>
> Upgrade urgency: SECURITY, contains fixes to security issues.
>
> Security Fixes:
> * (CVE-2022-31144) A specially crafted XAUTOCLAIM command on a stream
> key in a specific state may result with heap overflow, and potentially
> remote code execution. The problem affects Redis versions 7.0.0 or newer.
>
> Signed-off-by: Titouan Christophe <titouanchristophe@gmail.com>
> ---
> package/redis/redis.hash | 2 +-
> package/redis/redis.mk | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
Applied to master, 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
next prev parent reply other threads:[~2022-08-11 20:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 18:54 [Buildroot] [PATCH 1/1] package/redis: security bump to v7.0.4 Titouan Christophe
2022-08-11 20:25 ` Thomas Petazzoni via buildroot [this message]
2022-09-14 22:36 ` Peter Korsgaard
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=20220811222513.7ef2b670@windsurf \
--to=buildroot@buildroot.org \
--cc=daniel.price@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=titouanchristophe@gmail.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