buildroot.buildroot.org archive mirror
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.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: bump to v7.0.3
Date: Wed, 10 Aug 2022 12:37:16 +0200	[thread overview]
Message-ID: <871qtoqt9f.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20220712114510.1434413-1-titouanchristophe@gmail.com> (Titouan Christophe's message of "Tue, 12 Jul 2022 13:45:10 +0200")

>>>>> "Titouan" == Titouan Christophe <titouanchristophe@gmail.com> writes:

 > Signed-off-by: Titouan Christophe <titouanchristophe@gmail.com>

Committed to 2022.05.x given the fixes, thanks.

I see there is also a 7.0.4 release with security fixes, care to send a
patch?

================================================================================
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.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2022-08-10 10:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-12 11:45 [Buildroot] [PATCH 1/1] package/redis: bump to v7.0.3 Titouan Christophe
2022-07-17 13:21 ` Yann E. MORIN
2022-08-10 10:37 ` Peter Korsgaard [this message]
2022-08-11 19:00   ` Titouan Christophe
2022-08-11 19:20     ` 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=871qtoqt9f.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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;
as well as URLs for NNTP newsgroup(s).