dbcve.org
Secure Firewall Threat DefenseApplication · Cisco

CVE-2019-1714

HIGH · 8.6 CVSS v3.1 Published 2019-05-03
Fix available
A fix is available. Upgrade to 6.2.3.12 / 6.3.0.3 or later.
See remediation →
95/100
Remediation priority · Urgent
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 implementation of Security Assertion Markup Language (SAML) 2.0 Single Sign-On (SSO) for Clientless SSL VPN (WebVPN) and AnyConnect Remote Access VPN in Cisco Adaptive Security Appliance (ASA) Software and Cisco Firepower Threat Defense (FTD) Software could allow an unauthenticated, remote attacker to successfully establish a VPN session to an affected device. The vulnerability is due to improper credential management when using NT LAN Manager (NTLM) or basic authentication. An attacker could exploit this vulnerability by opening a VPN session to an affected device after another VPN user has successfully authenticated to the affected device via SAML SSO. A successful exploit could allow the attacker to connect to secured networks behind the affected 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

This vulnerability in Cisco ASA and FTD software allows an unauthenticated remote attacker to establish a VPN session by exploiting improper credential management when NTLM or basic authentication is used alongside SAML 2.0 SSO. The attacker can open a VPN session after a legitimate user has successfully authenticated via SAML SSO, bypassing authentication controls and gaining access to secured networks.

MitigationApply the vendor-supplied security updates from Cisco to patch the SAML SSO credential management flaw in affected ASA and FTD software versions.

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
Secure Firewall Threat DefenseApplication
Affected:>= 6.2.1, < 6.2.3.12>= 6.3.0, < 6.3.0.3
Adaptive Security Appliance SoftwareOperating system
Affected:>= 9.7, < 9.8.4>= 9.9, < 9.9.2.50>= 9.10, < 9.10.1.17

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
Changed
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/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 installed Cisco ASA software version
    Run 'show version' on the ASA CLI and note the software version number in the format X.X or X.X.X
    Affected if The installed version falls within any of these ranges: >= 9.7 and < 9.8.4; >= 9.9 and < 9.9.2.50; >= 9.10 and < 9.10.1.17
  2. Identify installed Cisco FTD software version
    Run 'show version' on the FTD device via FMC or directly on the FTD CLI and note the software version number
    Affected if The installed version falls within any of these ranges: >= 6.2.1 and < 6.2.3.12; >= 6.3.0 and < 6.3.0.3
  3. Check if VPN is configured on the device
    Run 'show vpn-sessiondb' or 'show running-config | include vpn' to see if any VPN tunnels or remote access VPN profiles are configured
    Affected if Any active VPN configuration exists on the device
  4. Verify SAML SSO is enabled for VPN authentication
    Run 'show running-config | include saml' or check the AAA configuration for 'sso saml' in the VPN group-policy or tunnel-group settings
    Affected if SAML 2.0 SSO authentication is configured for VPN access
  5. Confirm secondary authentication method is NTLM or basic
    Run 'show running-config' and examine the authentication commands in the VPN tunnel-group or group-policy for 'authentication' commands using 'ntlm' or 'authentication-server-group' with local 'basic' fallback
    Affected if The VPN authentication is configured to use NTLM or basic authentication in combination with SAML SSO

A device is affected if it runs a vulnerable ASA or FTD version AND has a VPN configured that uses SAML 2.0 SSO together with NTLM or basic authentication as the secondary authentication method.

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 the vendor-supplied security updates from Cisco to patch the SAML SSO credential management flaw in affected ASA and FTD software versions.

Fix this in Secure Firewall Threat Defense 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-1714 — 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-1714 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