CVE-2016-7056: Medium severity Google Android vulnerability
A timing attack flaw was found in OpenSSL 1.0.1u and before that could allow a malicious user with local access to recover ECDSA P-256 private keys.
Other sources
The signing function in crypto/ecdsa/ecdsaossl.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 BNFLGCONSTTIME flag for nonces, failing to take a secure code path in the BNmodinverse method and therefore resulting in a cache-timing attack vulnerability. A malicious user with local access can recover ECDSA P-256 private keys.
References:
http://seclists.org/oss-sec/2017/q1/52 http://eprint.iacr.org/2016/1195
— Red Hat
Affected Software
Remediation
Patch Available
Patch Available
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2016-7056?
CVE-2016-7056 has a high severity rating due to its potential to allow local users to recover private keys.
How do I fix CVE-2016-7056?
To fix CVE-2016-7056, update OpenSSL to versions 1.1.1w or later, or apply relevant patches provided by your Linux distribution.
Which versions of OpenSSL are affected by CVE-2016-7056?
CVE-2016-7056 affects OpenSSL versions 1.0.1u and earlier.
Can CVE-2016-7056 be exploited remotely?
CVE-2016-7056 cannot be exploited remotely as it requires local access to the vulnerable system.
What is the impact of a successful exploit of CVE-2016-7056?
A successful exploit of CVE-2016-7056 may allow an attacker to recover ECDSA P-256 private keys, compromising the security of encrypted communications.