# CVE-2019-1714: Auth bypass in Cisco Adaptive Security Appliance (ASA) Software

> Unauthenticated attackers can bypass SAML SSO authentication to establish VPN sessions and access secured networks behind Cisco ASA or FTD devices.

- **Severity:** Medium 5.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 May 2019
- **Updated:** 19 Nov 2024
- **Also known as:** GHSA-c2pv-f87v-p3wc

## What is CVE-2019-1714?

CVE-2019-1714 is a medium-severity authentication bypass vulnerability in Cisco Adaptive Security Appliance Software, published on 3 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-255

## Which versions are affected by CVE-2019-1714?

It affects 2 products.


Products: Cisco Adaptive Security Appliance Software, Cisco Secure Firewall Threat Defense.

## How do I fix CVE-2019-1714?

No fix has been published for CVE-2019-1714 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-1714 being exploited?

There is no known exploitation of CVE-2019-1714 in the wild and no public exploit code.

## Other vulnerabilities in Cisco Adaptive Security Appliance Software

- [CVE-2025-20333](https://insights.sbomify.com/CVE-2025-20333/): Cisco Secure Firewall Adaptive Security Appliance (ASA) and Secure Firewall Threat Defense (FTD) Buffer Overflow (critical 9.9, exploited in the wild)
- [CVE-2016-6366](https://insights.sbomify.com/CVE-2016-6366/): Cisco Adaptive Security Appliance (ASA) SNMP Buffer Overflow (high 8.8, exploited in the wild)
- [CVE-2026-20349](https://insights.sbomify.com/CVE-2026-20349/): Cisco Secure Firewall Adaptive Security Appliance (ASA) and Secure Firewall Threat Defense (FTD) Heap Inspection (high 8.6, exploited in the wild)
- [CVE-2024-20353](https://insights.sbomify.com/CVE-2024-20353/): Cisco ASA and FTD Denial of Service (high 8.6, exploited in the wild)
- [CVE-2016-6367](https://insights.sbomify.com/CVE-2016-6367/): Cisco Adaptive Security Appliance (ASA) CLI Remote Code Execution (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-1714 and fix it if it is affected.

What it is: CVE-2019-1714 is a medium-severity authentication bypass vulnerability in Cisco Adaptive Security Appliance Software, published on 3 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-1714 in the wild and no public exploit code.

Affected product: Cisco Adaptive Security Appliance Software. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-1714/ (Markdown: https://insights.sbomify.com/CVE-2019-1714/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-1714
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-1714
- OSV: https://osv.dev/vulnerability/CVE-2019-1714

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-1714/
Summaries are generated and may contain mistakes; the official description above is the record.