From: Leo Famulari <leo@famulari.name>
Cc: 31831-done@debbugs.gnu.org
Subject: bug#31831: CVE-2018-0495 Key Extraction Side Channel in Multiple Crypto Libraries
Date: Mon, 25 Feb 2019 21:01:08 -0500 [thread overview]
Message-ID: <20190226020108.GA25161@jasmine.lan> (raw)
In-Reply-To: <20180716171430.GA20978@jasmine.lan>
[-- Attachment #1: Type: text/plain, Size: 896 bytes --]
On Mon, Jul 16, 2018 at 01:14:30PM -0400, Leo Famulari wrote:
> There is a new release of Crypto++ available. I'm not sure if this
> addresses whatever issue was mentioned in the original advisory.
Crypto++ was updated to 8.0.0 in January 2019.
https://www.cryptopp.com/release800.html
> mbedTLS's changelog doesn't mention anything related to key extraction
> side channels.
mbedTLS has been updated several times since this bug was opened, and is
currently at 2.16.0.
https://github.com/ARMmbed/mbedtls/blob/fb1972db23da39bd11d4f9c9ea6266eee665605b/ChangeLog
Neither of those upstreams have mentioned CVE-2018-0495, as far as I can
tell. The original advisory said they do not use the vulnerable pattern,
but do use "non-constant math, but different pattern".
Overall, I don't think there is anything left for us to do as a distro
in response to CVE-2018-0495, so I am closing this bug.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-02-26 2:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-14 19:22 bug#31831: CVE-2018-0495 Key Extraction Side Channel in Multiple Crypto Libraries Leo Famulari
2018-06-14 19:50 ` Leo Famulari
2018-06-14 19:53 ` Gábor Boskovits
2018-06-14 20:06 ` Leo Famulari
2018-06-14 20:44 ` Gábor Boskovits
2018-06-14 20:45 ` Leo Famulari
2018-06-18 16:35 ` Leo Famulari
2018-07-16 6:20 ` Leo Famulari
2018-07-16 6:53 ` Gábor Boskovits
2018-07-16 17:14 ` Leo Famulari
2018-07-16 17:39 ` Leo Famulari
2019-02-26 2:01 ` Leo Famulari [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190226020108.GA25161@jasmine.lan \
--to=leo@famulari.name \
--cc=31831-done@debbugs.gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).