CVE-2019-1715

mediumpriority · track · 31EPSS 0.017 · 77 %ileEURUUS

grimoire priorityP3 · Track

Exploitable?

—

no known exploitation

Likely / severe?

1.73% (77th) EPSS

CVSS 5 · medium

Is it mine?

48 products

Check your exposure

Who says so?

4 sources

cnnvd · enisa_euvd · fstec_bdu · cisco_csaf

EPSS · scored 2026-10-27

A vulnerability in the Deterministic Random Bit Generator (DRBG), also known as Pseudorandom Number Generator (PRNG), used in Cisco Adaptive Security Appliance (ASA) Software and Cisco Firepower Threat Defense (FTD) Software could allow an unauthenticated, remote attacker to cause a cryptographic collision, enabling the attacker to discover the private key of an affected device. The vulnerability is due to insufficient entropy in the DRBG when generating cryptographic keys. An attacker could exploit this vulnerability by generating a large number of cryptographic keys on an affected device and looking for collisions with target devices. A successful exploit could allow the attacker to impersonate an affected target device or to decrypt traffic secured by an affected key that is sent to or from an affected target device.

remediations

Vendor fix, mitigation, or workaround guidance, as published by each source.

A vendor fix is available.

Fixed6.2.1cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed6.2.2cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed6.2.2.1cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed6.2.2.2cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed6.2.2.3cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed6.2.2.4cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed6.2.3cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed6.2.3.1cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed6.2.3.2cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.8.1cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.8.1.5cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.8.1.7cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.8.2cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.8.2.10cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.8.2.11cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.8.2.14cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.8.2.15cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.8.2.17cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.8.2.18cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.8.2.19cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.8.2.20cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.8.2.24cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.8.2.26cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.8.2.28cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.8.2.3cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.8.2.33cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.8.2.35cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.8.2.38cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.8.2.8cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.9.1cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.9.1.2cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.9.1.3cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.9.1.4cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.9.2cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.9.2.1cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.9.2.9cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Workaround6.2.1cisco_csaf
To avoid the use of potentially weak cryptographic keys, administrators can generate a key pair and a corresponding certificate on a trusted device outside of the Cisco ASA or FTD device and then import the base 64 encoded PKCS #12 file containing the keys and certificate(s) to the Cisco ASA or FTD device using the crypto ca import <trust-point-name> pkcs12 <passphrase> command in global configuration mode. See the ASA 8.x: Renew and Install the SSL Certificate with ASDM ["https://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/107956-renew-ssl.html#proc"] tech note for further details, including steps for how to accomplish this task via the Cisco Adaptive Security Device Manager (ASDM).
Workaround6.2.2cisco_csaf
To avoid the use of potentially weak cryptographic keys, administrators can generate a key pair and a corresponding certificate on a trusted device outside of the Cisco ASA or FTD device and then import the base 64 encoded PKCS #12 file containing the keys and certificate(s) to the Cisco ASA or FTD device using the crypto ca import <trust-point-name> pkcs12 <passphrase> command in global configuration mode. See the ASA 8.x: Renew and Install the SSL Certificate with ASDM ["https://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/107956-renew-ssl.html#proc"] tech note for further details, including steps for how to accomplish this task via the Cisco Adaptive Security Device Manager (ASDM).
Workaround6.2.2.1cisco_csaf
To avoid the use of potentially weak cryptographic keys, administrators can generate a key pair and a corresponding certificate on a trusted device outside of the Cisco ASA or FTD device and then import the base 64 encoded PKCS #12 file containing the keys and certificate(s) to the Cisco ASA or FTD device using the crypto ca import <trust-point-name> pkcs12 <passphrase> command in global configuration mode. See the ASA 8.x: Renew and Install the SSL Certificate with ASDM ["https://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/107956-renew-ssl.html#proc"] tech note for further details, including steps for how to accomplish this task via the Cisco Adaptive Security Device Manager (ASDM).
Workaround6.2.2.2cisco_csaf
To avoid the use of potentially weak cryptographic keys, administrators can generate a key pair and a corresponding certificate on a trusted device outside of the Cisco ASA or FTD device and then import the base 64 encoded PKCS #12 file containing the keys and certificate(s) to the Cisco ASA or FTD device using the crypto ca import <trust-point-name> pkcs12 <passphrase> command in global configuration mode. See the ASA 8.x: Renew and Install the SSL Certificate with ASDM ["https://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/107956-renew-ssl.html#proc"] tech note for further details, including steps for how to accomplish this task via the Cisco Adaptive Security Device Manager (ASDM).
Workaround6.2.2.3cisco_csaf
To avoid the use of potentially weak cryptographic keys, administrators can generate a key pair and a corresponding certificate on a trusted device outside of the Cisco ASA or FTD device and then import the base 64 encoded PKCS #12 file containing the keys and certificate(s) to the Cisco ASA or FTD device using the crypto ca import <trust-point-name> pkcs12 <passphrase> command in global configuration mode. See the ASA 8.x: Renew and Install the SSL Certificate with ASDM ["https://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/107956-renew-ssl.html#proc"] tech note for further details, including steps for how to accomplish this task via the Cisco Adaptive Security Device Manager (ASDM).
Workaround6.2.2.4cisco_csaf
To avoid the use of potentially weak cryptographic keys, administrators can generate a key pair and a corresponding certificate on a trusted device outside of the Cisco ASA or FTD device and then import the base 64 encoded PKCS #12 file containing the keys and certificate(s) to the Cisco ASA or FTD device using the crypto ca import <trust-point-name> pkcs12 <passphrase> command in global configuration mode. See the ASA 8.x: Renew and Install the SSL Certificate with ASDM ["https://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/107956-renew-ssl.html#proc"] tech note for further details, including steps for how to accomplish this task via the Cisco Adaptive Security Device Manager (ASDM).
Workaround6.2.3cisco_csaf
To avoid the use of potentially weak cryptographic keys, administrators can generate a key pair and a corresponding certificate on a trusted device outside of the Cisco ASA or FTD device and then import the base 64 encoded PKCS #12 file containing the keys and certificate(s) to the Cisco ASA or FTD device using the crypto ca import <trust-point-name> pkcs12 <passphrase> command in global configuration mode. See the ASA 8.x: Renew and Install the SSL Certificate with ASDM ["https://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/107956-renew-ssl.html#proc"] tech note for further details, including steps for how to accomplish this task via the Cisco Adaptive Security Device Manager (ASDM).
Workaround6.2.3.1cisco_csaf
To avoid the use of potentially weak cryptographic keys, administrators can generate a key pair and a corresponding certificate on a trusted device outside of the Cisco ASA or FTD device and then import the base 64 encoded PKCS #12 file containing the keys and certificate(s) to the Cisco ASA or FTD device using the crypto ca import <trust-point-name> pkcs12 <passphrase> command in global configuration mode. See the ASA 8.x: Renew and Install the SSL Certificate with ASDM ["https://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/107956-renew-ssl.html#proc"] tech note for further details, including steps for how to accomplish this task via the Cisco Adaptive Security Device Manager (ASDM).
Workaround6.2.3.2cisco_csaf
To avoid the use of potentially weak cryptographic keys, administrators can generate a key pair and a corresponding certificate on a trusted device outside of the Cisco ASA or FTD device and then import the base 64 encoded PKCS #12 file containing the keys and certificate(s) to the Cisco ASA or FTD device using the crypto ca import <trust-point-name> pkcs12 <passphrase> command in global configuration mode. See the ASA 8.x: Renew and Install the SSL Certificate with ASDM ["https://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/107956-renew-ssl.html#proc"] tech note for further details, including steps for how to accomplish this task via the Cisco Adaptive Security Device Manager (ASDM).
Workaround9.8.1cisco_csaf
To avoid the use of potentially weak cryptographic keys, administrators can generate a key pair and a corresponding certificate on a trusted device outside of the Cisco ASA or FTD device and then import the base 64 encoded PKCS #12 file containing the keys and certificate(s) to the Cisco ASA or FTD device using the crypto ca import <trust-point-name> pkcs12 <passphrase> command in global configuration mode. See the ASA 8.x: Renew and Install the SSL Certificate with ASDM ["https://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/107956-renew-ssl.html#proc"] tech note for further details, including steps for how to accomplish this task via the Cisco Adaptive Security Device Manager (ASDM).
Workaround9.8.1.5cisco_csaf
To avoid the use of potentially weak cryptographic keys, administrators can generate a key pair and a corresponding certificate on a trusted device outside of the Cisco ASA or FTD device and then import the base 64 encoded PKCS #12 file containing the keys and certificate(s) to the Cisco ASA or FTD device using the crypto ca import <trust-point-name> pkcs12 <passphrase> command in global configuration mode. See the ASA 8.x: Renew and Install the SSL Certificate with ASDM ["https://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/107956-renew-ssl.html#proc"] tech note for further details, including steps for how to accomplish this task via the Cisco Adaptive Security Device Manager (ASDM).
Workaround9.8.1.7cisco_csaf
To avoid the use of potentially weak cryptographic keys, administrators can generate a key pair and a corresponding certificate on a trusted device outside of the Cisco ASA or FTD device and then import the base 64 encoded PKCS #12 file containing the keys and certificate(s) to the Cisco ASA or FTD device using the crypto ca import <trust-point-name> pkcs12 <passphrase> command in global configuration mode. See the ASA 8.x: Renew and Install the SSL Certificate with ASDM ["https://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/107956-renew-ssl.html#proc"] tech note for further details, including steps for how to accomplish this task via the Cisco Adaptive Security Device Manager (ASDM).
Workaround9.8.2cisco_csaf
To avoid the use of potentially weak cryptographic keys, administrators can generate a key pair and a corresponding certificate on a trusted device outside of the Cisco ASA or FTD device and then import the base 64 encoded PKCS #12 file containing the keys and certificate(s) to the Cisco ASA or FTD device using the crypto ca import <trust-point-name> pkcs12 <passphrase> command in global configuration mode. See the ASA 8.x: Renew and Install the SSL Certificate with ASDM ["https://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/107956-renew-ssl.html#proc"] tech note for further details, including steps for how to accomplish this task via the Cisco Adaptive Security Device Manager (ASDM).
Workaround9.8.2.10cisco_csaf
To avoid the use of potentially weak cryptographic keys, administrators can generate a key pair and a corresponding certificate on a trusted device outside of the Cisco ASA or FTD device and then import the base 64 encoded PKCS #12 file containing the keys and certificate(s) to the Cisco ASA or FTD device using the crypto ca import <trust-point-name> pkcs12 <passphrase> command in global configuration mode. See the ASA 8.x: Renew and Install the SSL Certificate with ASDM ["https://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/107956-renew-ssl.html#proc"] tech note for further details, including steps for how to accomplish this task via the Cisco Adaptive Security Device Manager (ASDM).
Workaround9.8.2.11cisco_csaf
To avoid the use of potentially weak cryptographic keys, administrators can generate a key pair and a corresponding certificate on a trusted device outside of the Cisco ASA or FTD device and then import the base 64 encoded PKCS #12 file containing the keys and certificate(s) to the Cisco ASA or FTD device using the crypto ca import <trust-point-name> pkcs12 <passphrase> command in global configuration mode. See the ASA 8.x: Renew and Install the SSL Certificate with ASDM ["https://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/107956-renew-ssl.html#proc"] tech note for further details, including steps for how to accomplish this task via the Cisco Adaptive Security Device Manager (ASDM).
Workaround9.8.2.14cisco_csaf
To avoid the use of potentially weak cryptographic keys, administrators can generate a key pair and a corresponding certificate on a trusted device outside of the Cisco ASA or FTD device and then import the base 64 encoded PKCS #12 file containing the keys and certificate(s) to the Cisco ASA or FTD device using the crypto ca import <trust-point-name> pkcs12 <passphrase> command in global configuration mode. See the ASA 8.x: Renew and Install the SSL Certificate with ASDM ["https://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/107956-renew-ssl.html#proc"] tech note for further details, including steps for how to accomplish this task via the Cisco Adaptive Security Device Manager (ASDM).
Workaround9.8.2.15cisco_csaf
To avoid the use of potentially weak cryptographic keys, administrators can generate a key pair and a corresponding certificate on a trusted device outside of the Cisco ASA or FTD device and then import the base 64 encoded PKCS #12 file containing the keys and certificate(s) to the Cisco ASA or FTD device using the crypto ca import <trust-point-name> pkcs12 <passphrase> command in global configuration mode. See the ASA 8.x: Renew and Install the SSL Certificate with ASDM ["https://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/107956-renew-ssl.html#proc"] tech note for further details, including steps for how to accomplish this task via the Cisco Adaptive Security Device Manager (ASDM).
Workaround9.8.2.17cisco_csaf
To avoid the use of potentially weak cryptographic keys, administrators can generate a key pair and a corresponding certificate on a trusted device outside of the Cisco ASA or FTD device and then import the base 64 encoded PKCS #12 file containing the keys and certificate(s) to the Cisco ASA or FTD device using the crypto ca import <trust-point-name> pkcs12 <passphrase> command in global configuration mode. See the ASA 8.x: Renew and Install the SSL Certificate with ASDM ["https://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/107956-renew-ssl.html#proc"] tech note for further details, including steps for how to accomplish this task via the Cisco Adaptive Security Device Manager (ASDM).
Workaround9.8.2.18cisco_csaf
To avoid the use of potentially weak cryptographic keys, administrators can generate a key pair and a corresponding certificate on a trusted device outside of the Cisco ASA or FTD device and then import the base 64 encoded PKCS #12 file containing the keys and certificate(s) to the Cisco ASA or FTD device using the crypto ca import <trust-point-name> pkcs12 <passphrase> command in global configuration mode. See the ASA 8.x: Renew and Install the SSL Certificate with ASDM ["https://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/107956-renew-ssl.html#proc"] tech note for further details, including steps for how to accomplish this task via the Cisco Adaptive Security Device Manager (ASDM).
Workaround9.8.2.19cisco_csaf
To avoid the use of potentially weak cryptographic keys, administrators can generate a key pair and a corresponding certificate on a trusted device outside of the Cisco ASA or FTD device and then import the base 64 encoded PKCS #12 file containing the keys and certificate(s) to the Cisco ASA or FTD device using the crypto ca import <trust-point-name> pkcs12 <passphrase> command in global configuration mode. See the ASA 8.x: Renew and Install the SSL Certificate with ASDM ["https://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/107956-renew-ssl.html#proc"] tech note for further details, including steps for how to accomplish this task via the Cisco Adaptive Security Device Manager (ASDM).
Workaround9.8.2.20cisco_csaf
To avoid the use of potentially weak cryptographic keys, administrators can generate a key pair and a corresponding certificate on a trusted device outside of the Cisco ASA or FTD device and then import the base 64 encoded PKCS #12 file containing the keys and certificate(s) to the Cisco ASA or FTD device using the crypto ca import <trust-point-name> pkcs12 <passphrase> command in global configuration mode. See the ASA 8.x: Renew and Install the SSL Certificate with ASDM ["https://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/107956-renew-ssl.html#proc"] tech note for further details, including steps for how to accomplish this task via the Cisco Adaptive Security Device Manager (ASDM).
Workaround9.8.2.24cisco_csaf
To avoid the use of potentially weak cryptographic keys, administrators can generate a key pair and a corresponding certificate on a trusted device outside of the Cisco ASA or FTD device and then import the base 64 encoded PKCS #12 file containing the keys and certificate(s) to the Cisco ASA or FTD device using the crypto ca import <trust-point-name> pkcs12 <passphrase> command in global configuration mode. See the ASA 8.x: Renew and Install the SSL Certificate with ASDM ["https://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/107956-renew-ssl.html#proc"] tech note for further details, including steps for how to accomplish this task via the Cisco Adaptive Security Device Manager (ASDM).
Workaround9.8.2.26cisco_csaf
To avoid the use of potentially weak cryptographic keys, administrators can generate a key pair and a corresponding certificate on a trusted device outside of the Cisco ASA or FTD device and then import the base 64 encoded PKCS #12 file containing the keys and certificate(s) to the Cisco ASA or FTD device using the crypto ca import <trust-point-name> pkcs12 <passphrase> command in global configuration mode. See the ASA 8.x: Renew and Install the SSL Certificate with ASDM ["https://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/107956-renew-ssl.html#proc"] tech note for further details, including steps for how to accomplish this task via the Cisco Adaptive Security Device Manager (ASDM).
Workaround9.8.2.28cisco_csaf
To avoid the use of potentially weak cryptographic keys, administrators can generate a key pair and a corresponding certificate on a trusted device outside of the Cisco ASA or FTD device and then import the base 64 encoded PKCS #12 file containing the keys and certificate(s) to the Cisco ASA or FTD device using the crypto ca import <trust-point-name> pkcs12 <passphrase> command in global configuration mode. See the ASA 8.x: Renew and Install the SSL Certificate with ASDM ["https://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/107956-renew-ssl.html#proc"] tech note for further details, including steps for how to accomplish this task via the Cisco Adaptive Security Device Manager (ASDM).
Workaround9.8.2.3cisco_csaf
To avoid the use of potentially weak cryptographic keys, administrators can generate a key pair and a corresponding certificate on a trusted device outside of the Cisco ASA or FTD device and then import the base 64 encoded PKCS #12 file containing the keys and certificate(s) to the Cisco ASA or FTD device using the crypto ca import <trust-point-name> pkcs12 <passphrase> command in global configuration mode. See the ASA 8.x: Renew and Install the SSL Certificate with ASDM ["https://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/107956-renew-ssl.html#proc"] tech note for further details, including steps for how to accomplish this task via the Cisco Adaptive Security Device Manager (ASDM).
Workaround9.8.2.33cisco_csaf
To avoid the use of potentially weak cryptographic keys, administrators can generate a key pair and a corresponding certificate on a trusted device outside of the Cisco ASA or FTD device and then import the base 64 encoded PKCS #12 file containing the keys and certificate(s) to the Cisco ASA or FTD device using the crypto ca import <trust-point-name> pkcs12 <passphrase> command in global configuration mode. See the ASA 8.x: Renew and Install the SSL Certificate with ASDM ["https://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/107956-renew-ssl.html#proc"] tech note for further details, including steps for how to accomplish this task via the Cisco Adaptive Security Device Manager (ASDM).
Workaround9.8.2.35cisco_csaf
To avoid the use of potentially weak cryptographic keys, administrators can generate a key pair and a corresponding certificate on a trusted device outside of the Cisco ASA or FTD device and then import the base 64 encoded PKCS #12 file containing the keys and certificate(s) to the Cisco ASA or FTD device using the crypto ca import <trust-point-name> pkcs12 <passphrase> command in global configuration mode. See the ASA 8.x: Renew and Install the SSL Certificate with ASDM ["https://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/107956-renew-ssl.html#proc"] tech note for further details, including steps for how to accomplish this task via the Cisco Adaptive Security Device Manager (ASDM).
Workaround9.8.2.38cisco_csaf
To avoid the use of potentially weak cryptographic keys, administrators can generate a key pair and a corresponding certificate on a trusted device outside of the Cisco ASA or FTD device and then import the base 64 encoded PKCS #12 file containing the keys and certificate(s) to the Cisco ASA or FTD device using the crypto ca import <trust-point-name> pkcs12 <passphrase> command in global configuration mode. See the ASA 8.x: Renew and Install the SSL Certificate with ASDM ["https://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/107956-renew-ssl.html#proc"] tech note for further details, including steps for how to accomplish this task via the Cisco Adaptive Security Device Manager (ASDM).
Workaround9.8.2.8cisco_csaf
To avoid the use of potentially weak cryptographic keys, administrators can generate a key pair and a corresponding certificate on a trusted device outside of the Cisco ASA or FTD device and then import the base 64 encoded PKCS #12 file containing the keys and certificate(s) to the Cisco ASA or FTD device using the crypto ca import <trust-point-name> pkcs12 <passphrase> command in global configuration mode. See the ASA 8.x: Renew and Install the SSL Certificate with ASDM ["https://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/107956-renew-ssl.html#proc"] tech note for further details, including steps for how to accomplish this task via the Cisco Adaptive Security Device Manager (ASDM).
Workaround9.9.1cisco_csaf
To avoid the use of potentially weak cryptographic keys, administrators can generate a key pair and a corresponding certificate on a trusted device outside of the Cisco ASA or FTD device and then import the base 64 encoded PKCS #12 file containing the keys and certificate(s) to the Cisco ASA or FTD device using the crypto ca import <trust-point-name> pkcs12 <passphrase> command in global configuration mode. See the ASA 8.x: Renew and Install the SSL Certificate with ASDM ["https://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/107956-renew-ssl.html#proc"] tech note for further details, including steps for how to accomplish this task via the Cisco Adaptive Security Device Manager (ASDM).
Workaround9.9.1.2cisco_csaf
To avoid the use of potentially weak cryptographic keys, administrators can generate a key pair and a corresponding certificate on a trusted device outside of the Cisco ASA or FTD device and then import the base 64 encoded PKCS #12 file containing the keys and certificate(s) to the Cisco ASA or FTD device using the crypto ca import <trust-point-name> pkcs12 <passphrase> command in global configuration mode. See the ASA 8.x: Renew and Install the SSL Certificate with ASDM ["https://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/107956-renew-ssl.html#proc"] tech note for further details, including steps for how to accomplish this task via the Cisco Adaptive Security Device Manager (ASDM).
Workaround9.9.1.3cisco_csaf
To avoid the use of potentially weak cryptographic keys, administrators can generate a key pair and a corresponding certificate on a trusted device outside of the Cisco ASA or FTD device and then import the base 64 encoded PKCS #12 file containing the keys and certificate(s) to the Cisco ASA or FTD device using the crypto ca import <trust-point-name> pkcs12 <passphrase> command in global configuration mode. See the ASA 8.x: Renew and Install the SSL Certificate with ASDM ["https://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/107956-renew-ssl.html#proc"] tech note for further details, including steps for how to accomplish this task via the Cisco Adaptive Security Device Manager (ASDM).
Workaround9.9.1.4cisco_csaf
To avoid the use of potentially weak cryptographic keys, administrators can generate a key pair and a corresponding certificate on a trusted device outside of the Cisco ASA or FTD device and then import the base 64 encoded PKCS #12 file containing the keys and certificate(s) to the Cisco ASA or FTD device using the crypto ca import <trust-point-name> pkcs12 <passphrase> command in global configuration mode. See the ASA 8.x: Renew and Install the SSL Certificate with ASDM ["https://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/107956-renew-ssl.html#proc"] tech note for further details, including steps for how to accomplish this task via the Cisco Adaptive Security Device Manager (ASDM).
Workaround9.9.2cisco_csaf
To avoid the use of potentially weak cryptographic keys, administrators can generate a key pair and a corresponding certificate on a trusted device outside of the Cisco ASA or FTD device and then import the base 64 encoded PKCS #12 file containing the keys and certificate(s) to the Cisco ASA or FTD device using the crypto ca import <trust-point-name> pkcs12 <passphrase> command in global configuration mode. See the ASA 8.x: Renew and Install the SSL Certificate with ASDM ["https://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/107956-renew-ssl.html#proc"] tech note for further details, including steps for how to accomplish this task via the Cisco Adaptive Security Device Manager (ASDM).
Workaround9.9.2.1cisco_csaf
To avoid the use of potentially weak cryptographic keys, administrators can generate a key pair and a corresponding certificate on a trusted device outside of the Cisco ASA or FTD device and then import the base 64 encoded PKCS #12 file containing the keys and certificate(s) to the Cisco ASA or FTD device using the crypto ca import <trust-point-name> pkcs12 <passphrase> command in global configuration mode. See the ASA 8.x: Renew and Install the SSL Certificate with ASDM ["https://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/107956-renew-ssl.html#proc"] tech note for further details, including steps for how to accomplish this task via the Cisco Adaptive Security Device Manager (ASDM).
Workaround9.9.2.9cisco_csaf
To avoid the use of potentially weak cryptographic keys, administrators can generate a key pair and a corresponding certificate on a trusted device outside of the Cisco ASA or FTD device and then import the base 64 encoded PKCS #12 file containing the keys and certificate(s) to the Cisco ASA or FTD device using the crypto ca import <trust-point-name> pkcs12 <passphrase> command in global configuration mode. See the ASA 8.x: Renew and Install the SSL Certificate with ASDM ["https://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/107956-renew-ssl.html#proc"] tech note for further details, including steps for how to accomplish this task via the Cisco Adaptive Security Device Manager (ASDM).

cvss

Technical severity, 0–10. One row per scoring source.

7.5

010

base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · medium–high · 5–7.5

v2.05mediumAV:N/AC:L/Au:N/C:P/I:N/A:Nprimary · NVD / NIST USexploitability 10 · impact 2.9

v3.07.5highCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:Nprimary · NVD / NIST USexploitability 3.9 · impact 3.6

v3.05.3mediumCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:Nsecondary · ENISA EU

v3.05.3mediumCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:Nsecondary · Cisco PSIRT US

v3.05.3mediumCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:Nsecondary · psirt@cisco.com USexploitability 3.9 · impact 1.4

v3.06.9mediumCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N/E:Usecondary · CVSS-BT (t0sche)

v3.15.3mediumAV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:Nsecondary · FSTEC (BDU) RU

ssvc

A stakeholder decision — act, attend, or track — from exploitation and impact.

Exploitation: none · Automatable: yes · Technical Impact: partialcoordinatorcisa_ssvcUS

weaknesses

The CWE weakness classes this flaw belongs to.

CWE-332USprimaryCWE-332US

affected products (48)

Products and version ranges known to be affected.

showing 20 of 48

advisories (1)

Vendor and ecosystem advisories describing this.

cisco-sa-20190501-asa-ftd-entropyCisco Adaptive Security Appliance Software and Firepower Threat Defense Software Low-Entropy Keys Vulnerability2019-05-01csaf · cisco_csafUS
A vulnerability in the Deterministic Random Bit Generator (DRBG), also known as Pseudorandom Number Generator (PRNG), used in Cisco Adaptive Security Appliance (ASA) Software and Cisco Firepower Threat Defense (FTD) Software could allow an unauthenticated, remote attacker to cause a cryptographic collision, enabling the attacker to discover the private key of an affected device. The vulnerability is due to insufficient entropy in the DRBG when generating cryptographic keys. An attacker could exploit this vulnerability by generating a large number of cryptographic keys on an affected device and looking for collisions with target devices. A successful exploit could allow the attacker to impersonate an affected target device or to decrypt traffic secured by an affected key that is sent to or from an affected target device. Cisco has released software updates that address this vulnerability. There are workarounds that address this vulnerability.

also known as (4)

Other names and identifiers for this entity.

sources

Which sources assert this record, and when.

cnnvd enisa_euvd fstec_bdu cisco_csaf NVD CVE.org MITRE

published 2019-05-03modified 2026-08-11

related (13)

Related entries.

ID	severity	EPSS	exploitable	published
CVE-2018-9057US	critical9.8	1.92% (80th)	—	2018-03-27
aws/resource_aws_iam_user_login_profile.go in the HashiCorp Terraform Amazon Web Services (AWS) provider through v1.12.0 has an inappropriate PRNG algorithm and seeding, which make…
CVE-2016-15005US	high8.8	0.41% (36th)	—	2022-12-27
CSRF tokens are generated using math/rand, which is not a cryptographically secure random number generator, allowing an attacker to predict values and bypass CSRF protections with…
CVE-2017-18486US	high7.2	4.81% (92nd)	—	2019-08-09
Jitbit Helpdesk before 9.0.3 allows remote attackers to escalate privileges because of mishandling of the User/AutoLogin userHash parameter. By inspecting the token value provided…
CVE-2016-10743US	high7.5	2.35% (84th)	—	2019-03-23
hostapd before 2.6 does not prevent use of the low-quality PRNG that is reached by an os_random() function call.
CVE-2016-9154US	high7.5	1.50% (74th)	—	2016-12-23
Siemens Desigo PX Web modules PXA40-W0, PXA40-W1, PXA40-W2 for Desigo PX automation controllers PXC00-E.D, PXC50-E.D, PXC100-E.D, PXC200-E.D (All firmware versions < V6.00.046) and…

+8 more

references (7)

External citations — patches, advisories, analysis.

scry

Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.

Free scan