From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
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.5
Date: Mon, 26 Sep 2022 14:02:52 +0200 [thread overview]
Message-ID: <20220926140252.2f775240@windsurf> (raw)
In-Reply-To: <20220926101724.1989377-1-titouanchristophe@gmail.com>
On Mon, 26 Sep 2022 12:17:24 +0200
Titouan Christophe <titouanchristophe@gmail.com> wrote:
> From the release notes:
> (https://github.com/redis/redis/blob/7.0.5/00-RELEASENOTES)
>
> ================================================================================
> Redis 7.0.5 Released Wed Sep 21 20:00:00 IST 2022
> ================================================================================
>
> Upgrade urgency: SECURITY, contains fixes to security issues.
>
> Security Fixes:
> * (CVE-2022-35951) Executing a XAUTOCLAIM command on a stream key in a specific
> state, with a specially crafted COUNT argument, may cause an integer overflow,
> a subsequent heap overflow, and potentially lead to remote code execution.
> The problem affects Redis versions 7.0.0 or newer
> [reported by Xion (SeungHyun Lee) of KAIST GoN].
>
> 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-09-26 12:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 10:17 [Buildroot] [PATCH 1/1] package/redis: security bump to v7.0.5 Titouan Christophe
2022-09-26 12:02 ` Thomas Petazzoni [this message]
2022-10-11 19:23 ` 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=20220926140252.2f775240@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=daniel.price@gmail.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