dbcve.org
Adaptive Security Appliance Device ManagerApplication · Cisco

CVE-2019-1715

HIGH · 7.5 CVSS v3.0 Published 2019-05-03
Fix available
A fix is available. Upgrade to 6.2.3.12 / 6.3.0.3 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The DRBG/PRNG in Cisco ASA and FTD software suffers from insufficient entropy during cryptographic key generation. This allows an unauthenticated remote attacker to generate large numbers of keys and identify collisions with target device keys, enabling private key discovery and subsequent impersonation or traffic decryption.

MitigationApply Cisco-provided patches for ASA and FTD software once available. Prioritize updating devices with externally-facing services that rely on affected cryptographic keys.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Adaptive Security Appliance Device ManagerApplication
Affected:>= 9.8, < 9.8.4>= 9.9, < 9.9.2.50
Secure Firewall Threat DefenseApplication
Affected:>= 6.2.1, < 6.2.3.12>= 6.3.0, < 6.3.0.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Cisco ASA or FTD software version
    Run 'show version' or 'show version | include Version' on the device CLI to obtain the running software version
    Affected if The displayed version falls within the affected ranges: ASA versions 9.8.x before 9.8.4, or 9.9.x before 9.9.2.50; FTD versions 6.2.1.x before 6.2.3.12, or 6.3.0.x before 6.3.0.3
  2. Confirm the product type
    Run 'show version' and identify whether the output shows 'Adaptive Security Appliance' or 'Firepower Threat Defense'
    Affected if The device is running Cisco ASA or FTD software matching the version ranges in step 1
  3. Determine if VPN or SSL-based services are configured
    Run 'show vpn-sessiondb' or 'show run | include crypto|ssl|ipsec' to check for active VPN, SSL VPN, or IPSec configurations that rely on dynamically generated cryptographic keys
    Affected if The device has VPN, SSL VPN, or IPSec tunnels configured that use dynamically generated keys from the affected software version
  4. Check for externally accessible services using affected crypto
    Run 'show interface' and review 'show run' for external interfaces with SSL/IPSec services enabled. Verify if the device has public IP addresses assigned to affected interfaces
    Affected if The device has externally-facing interfaces with SSL, VPN, or IPSec services configured using keys generated by the affected software

A device is affected if it runs Cisco ASA or FTD software versions within the specified ranges AND has VPN, SSL, or IPSec services configured that rely on the cryptographic key generation affected by the insufficient entropy flaw.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 6.2.3.12 / 6.3.0.3 / 9.8.4 or later
Fixed in 6.2.3.126.3.0.39.8.4
Interim mitigation

Apply Cisco-provided patches for ASA and FTD software once available. Prioritize updating devices with externally-facing services that rely on affected cryptographic keys.

Fix this in Adaptive Security Appliance Device Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-1715 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-1715 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data