Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@buildroot.org
Cc: Matt Weber <matthew.weber@collins.com>
Subject: Re: [Buildroot] [PATCH] package/libopenssl: security bump to version 1.1.1q
Date: Sun, 31 Jul 2022 08:18:43 +0200	[thread overview]
Message-ID: <87mtcppzy4.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <87let38iaf.fsf@dell.be.48ers.dk> (Peter Korsgaard's message of "Fri, 08 Jul 2022 22:24:08 +0200")

>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
 >> Fixes the following security issues:
 >> AES OCB fails to encrypt some bytes (CVE-2022-2097)
 >> ===================================================

 >> Severity: MODERATE

 >> AES OCB mode for 32-bit x86 platforms using the AES-NI assembly optimised
 >> implementation will not encrypt the entirety of the data under some
 >> circumstances.  This could reveal sixteen bytes of data that was
 >> preexisting in the memory that wasn't written.  In the special case of
 >> "in place" encryption, sixteen bytes of the plaintext would be revealed.

 >> Since OpenSSL does not support OCB based cipher suites for TLS and DTLS,
 >> they are both unaffected.

 >> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>

Committed to 2022.05.x and 2022.02.x, thanks.

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

      reply	other threads:[~2022-07-31  6:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-08  7:17 [Buildroot] [PATCH] package/libopenssl: security bump to version 1.1.1q Peter Korsgaard
2022-07-08 20:24 ` Peter Korsgaard
2022-07-31  6:18   ` 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=87mtcppzy4.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=matthew.weber@collins.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