From: Leo Famulari <leo@famulari.name>
To: guix-devel@gnu.org
Subject: OpenSSL / LibreSSL CVE-2016-7056
Date: Tue, 10 Jan 2017 13:16:52 -0500 [thread overview]
Message-ID: <20170110181652.GA28153@jasmine> (raw)
CVE-2016-7056 has been published:
http://seclists.org/oss-sec/2017/q1/52
Quoted from that email:
Attack Vector: Local
Vendor: OpenSSL, LibreSSL, BoringSSL
Versions Affected:
OpenSSL 1.0.1u and previous versions
LibreSSL (pre 6.0 errata 16, pre 5.9 errata 33)
BoringSSL pre November 2015
Description:
The signing function in crypto/ecdsa/ecdsa_ossl.c in certain OpenSSL versions and forks
is vulnerable to timing attacks when signing with the standardized elliptic
curve P-256 despite featuring constant-time curve operations and modular inversion.
A software defect omits setting the BN_FLG_CONSTTIME flag for nonces, failing
to take a secure code path in the BN_mod_inverse method and therefore resulting
in a cache-timing attack vulnerability.
A malicious user with local access can recover ECDSA P-256 private keys.
Mitigation:
Users of OpenSSL with the affected versions should apply
the patch available in the manuscript at [1].
Users of LibreSSL should apply the official patch from OpenBSD [2,3].
Users of BoringSSL should upgrade to a more recent version.
Credit:
This issue was reported by Cesar Pereida García and Billy Brumley
(Tampere University of Technology).
Timeline:
19 Dec 2016 Disclosure to OpenSSL, LibreSSL, BoringSSL security teams
29 Dec 2016 Embargo lifted
References:
[1] http://ia.cr/2016/1195
[2] https://ftp.openbsd.org/pub/OpenBSD/patches/5.9/common/033_libcrypto.patch.sig
[3] https://ftp.openbsd.org/pub/OpenBSD/patches/6.0/common/016_libcrypto.patch.sig
reply other threads:[~2017-01-10 18:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20170110181652.GA28153@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.