CVE-2016-0701

Description

The DH_check_pub_key function in crypto/dh/dh_check.c in OpenSSL 1.0.2 before 1.0.2f does not ensure that prime numbers are appropriate for Diffie-Hellman (DH) key exchange, which makes it easier for remote attackers to discover a private DH exponent by making multiple handshakes with a peer that chose an inappropriate number, as demonstrated by a number in an X9.42 file.

Category

3.7
CVSS
Severity: Low
CVSS 3.0 •
CVSS 2.0 •
EPSS 24.99% Top 5%
Vendor Advisory fedoraproject.org Vendor Advisory gentoo.org Vendor Advisory opensuse.org Vendor Advisory ubuntu.com Vendor Advisory openssl.org
Affected: n/a n/a
Published at:
Updated at:

References

Link Tags
http://lists.fedoraproject.org/pipermail/package-announce/2016-January/176373.html vendor advisory
http://www.securitytracker.com/id/1034849 vdb entry
https://security.gentoo.org/glsa/201601-05 vendor advisory
http://www.securityfocus.com/bid/82233 vdb entry
http://www.securityfocus.com/bid/91787 vdb entry
https://www.kb.cert.org/vuls/id/257823 third party advisory
http://lists.opensuse.org/opensuse-security-announce/2016-03/msg00009.html vendor advisory
http://www.ubuntu.com/usn/USN-2883-1 vendor advisory
https://www.oracle.com/security-alerts/cpuapr2020.html
https://www.oracle.com/security-alerts/cpujul2020.html
https://www.oracle.com/technetwork/security-advisory/cpujul2019-5072835.html
https://www.oracle.com/security-alerts/cpujan2020.html
http://www.oracle.com/technetwork/security-advisory/cpujul2016-2881720.html
https://git.openssl.org/?p=openssl.git%3Ba=commit%3Bh=c5b831f21d0d29d1e517d139d9d101763f60c9a2
https://git.openssl.org/?p=openssl.git%3Ba=commit%3Bh=878e2c5b13010329c203f309ed0c8f2113f85648
https://h20566.www2.hpe.com/portal/site/hpsc/public/kb/docDisplay?docId=emr_na-c05164821
http://www.openssl.org/news/secadv/20160128.txt vendor advisory
http://www.oracle.com/technetwork/security-advisory/cpuoct2017-3236626.html
https://h20566.www2.hpe.com/portal/site/hpsc/public/kb/docDisplay?docId=emr_na-c05390893
http://intothesymmetry.blogspot.com/2016/01/openssl-key-recovery-attack-on-dh-small.html
https://h20566.www2.hpe.com/hpsc/doc/public/display?docLocale=en_US&docId=emr_na-hpesbhf03724en_us
http://kb.juniper.net/InfoCenter/index?page=content&id=JSA10759
https://www.oracle.com/security-alerts/cpuoct2020.html
https://cert-portal.siemens.com/productcert/pdf/ssa-412672.pdf

Frequently Asked Questions

What is the severity of CVE-2016-0701?
CVE-2016-0701 has been scored as a low severity vulnerability.
How to fix CVE-2016-0701?
To fix CVE-2016-0701, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2016-0701 being actively exploited in the wild?
It is possible that CVE-2016-0701 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~25% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.