Vulnerability Note VU#274923
Dual_EC_DRBG output using untrusted curve constants may be predictable
Output of the Dual Elliptic Curve Deterministic Random Bit Generator (DUAL_EC_DRBG) algorithm may be predictable by an attacker who has chosen elliptic curve parameters in advance.
NIST SP 800-90A defines three elliptic curves for use in Dual_EC_DBRG but does not describe the provenance of the parameters used to define the curves. Noted cryptographers and cryptographic vendors have expressed concern that an attacker who has carefully chosen parameters used to define the curves could predict the output of Dual_EC_DBRG. Due to these concerns, and since Dual_EC_DRBG is an approved Federal Information Processing Standard (FIPS), NIST has reopened Special Publication 800-90 for comment. The CERT/CC has contacted vendors that are identified by NIST as being FIPS-certified Dual_EC_DRBG implentors. We have included their responses below and in the Vendor Information section.
This issue is an instance of CWE-327: Use of a Broken or Risky Cryptographic Algorithm.
CERT/CC is not aware of any demonstrated or reported attacks against applications of Dual_EC_DRBG.
Based on responses from vendors and publicly available information, the following vendors do not use DUAL_EC_DRBG in their products:
The following vendors do use DUAL_EC_DRBG in their products, but it is not enabled by default:
The following vendors do use DUAL_EC_DRBG in their products, and it is enabled by default:
Further details for each vendor are available in the Vendor Information section below.
A remote, unauthenticated attacker with minimal knowledge of the vulnerable system and the ability to conduct a brute force attack against an affected application may be able to guess secret key material. Secondary impacts include authenticated access to the system through the affected service or the ability to perform man-in-the-middle attacks.
Apply an Update
Discontinue use of Dual_EC_DRBG
The NIST bulletin recommends organizations discontinue use of the algorithm until its security concerns are mitigated:
There are several other DRBG algorithms available for generating random numbers, including those based on hash functions and block ciphers. Utilizing one of those algorithms will mitigate the risk of this vulnerability.
Generate elliptic curves with known provenance
While not compatible with FIPS specifications, generating your own elliptic curves will provide assurance that random numbers cannot be predicted. See section A.2 of Appendix A in NIST SP 800-90A for more information.
Regenerate key material
Due to the nature of the flaw, any key material generated using Dual_EC_DRBG should be considered insecure. After changing algorithms or generating new curves, the key material must be regenerated. Vendor-specific instructions for doing this can also be found in the Vendor Information section of this document.
Vendor Information (Learn More)
|Vendor||Status||Date Notified||Date Updated|
|McAfee||Affected||03 Oct 2013||25 Mar 2014|
|Research in Motion (RIM)||Affected||03 Oct 2013||18 Feb 2014|
|RSA Security, Inc.||Affected||23 Sep 2013||16 Oct 2013|
|CatBird||Not Affected||06 Nov 2013||07 Nov 2013|
|Cisco Systems, Inc.||Not Affected||03 Oct 2013||07 Nov 2013|
|Cummings Engineering||Not Affected||08 Oct 2013||16 Oct 2013|
|Juniper Networks, Inc.||Not Affected||03 Oct 2013||07 Nov 2013|
|Lancope||Not Affected||07 Oct 2013||09 Dec 2013|
|Microsoft Corporation||Not Affected||03 Oct 2013||07 Nov 2013|
|Mocana||Not Affected||10 Oct 2013||07 Nov 2013|
|OpenSSL||Not Affected||03 Oct 2013||16 Oct 2013|
|SafeLogic||Not Affected||08 Oct 2013||16 Oct 2013|
|Panzura||Unknown||16 Oct 2013||16 Oct 2013|
|SafeNet||Unknown||03 Oct 2013||03 Oct 2013|
CVSS Metrics (Learn More)
Dan Shumow, Niels Ferguson (2007) and Daniel Brown (2006) published information related to this issue.
This document was written by Chris King.
- CVE IDs: CVE-2007-6755
- Date Public: 21 Aug 2007
- Date First Published: 07 Nov 2013
- Date Last Updated: 25 Mar 2014
- Document Revision: 53
If you have feedback, comments, or additional information about this vulnerability, please send us email.