From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/libopenssl: security bump to version 1.1.1c
Date: Fri, 31 May 2019 09:59:51 +0200 [thread overview]
Message-ID: <87lfynvytk.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20190530214336.16338-1-peter@korsgaard.com> (Peter Korsgaard's message of "Thu, 30 May 2019 23:43:36 +0200")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
> Fixes the following security issues:
> Prevent over long nonces in ChaCha20-Poly1305 (CVE-2019-1543)
> ChaCha20-Poly1305 is an AEAD cipher, and requires a unique nonce input for
> every encryption operation. RFC 7539 specifies that the nonce value (IV)
> should be 96 bits (12 bytes). OpenSSL allows a variable nonce length and
> front pads the nonce with 0 bytes if it is less than 12 bytes. However it
> also incorrectly allows a nonce to be set of up to 16 bytes. In this case
> only the last 12 bytes are significant and any additional leading bytes are
> ignored.
> It is a requirement of using this cipher that nonce values are unique.
> Messages encrypted using a reused nonce value are susceptible to serious
> confidentiality and integrity attacks. If an application changes the
> default nonce length to be longer than 12 bytes and then makes a change to
> the leading bytes of the nonce expecting the new value to be a new unique
> nonce then such an application could inadvertently encrypt messages with a
> reused nonce.
> Additionally the ignored bytes in a long nonce are not covered by the
> integrity guarantee of this cipher. Any application that relies on the
> integrity of these ignored leading bytes of a long nonce may be further
> affected. Any OpenSSL internal use of this cipher, including in SSL/TLS, is
> safe because no such use sets such a long nonce value. However user
> applications that use this cipher directly and set a non-default nonce
> length to be longer than 12 bytes may be vulnerable.
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Committed, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2019-05-31 7:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 21:43 [Buildroot] [PATCH] package/libopenssl: security bump to version 1.1.1c Peter Korsgaard
2019-05-31 7:59 ` Peter Korsgaard [this message]
2019-06-06 15:35 ` 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=87lfynvytk.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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