# CVE-2019-1713: Cisco Adaptive Security Appliance Software Cross-Site Request Forgery Vulnerability

> An unauthenticated remote attacker can perform arbitrary actions with the victim's privileges via CSRF, potentially altering configuration or reloading the device.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 May 2019
- **Updated:** 21 Nov 2024
- **Also known as:** GHSA-c2vh-w5p4-hr7q

## What is CVE-2019-1713?

CVE-2019-1713 is a high-severity vulnerability in Cisco Adaptive Security Appliance Software, published on 3 May 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability in the web-based management interface of Cisco Adaptive Security Appliance (ASA) Software could allow an unauthenticated, remote attacker to conduct a cross-site request forgery (CSRF) attack on an affected system. The vulnerability is due to insufficient CSRF protections for the web-based management interface on an affected device. An attacker could exploit this vulnerability by persuading a user of the interface to follow a malicious link. A successful exploit could allow the attacker to perform arbitrary actions with the privilege level of the affected user. If the user has administrative privileges, the attacker could alter the configuration of, extract information from, or reload an affected device.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Cisco Adaptive Security Appliance Software.

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

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

## Is CVE-2019-1713 being exploited?

There is no known exploitation of CVE-2019-1713 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-1713 and fix it if it is affected.

What it is: CVE-2019-1713 is a high-severity vulnerability in Cisco Adaptive Security Appliance Software, published on 3 May 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-1713 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-1713/ (Markdown: https://insights.sbomify.com/CVE-2019-1713/index.md)
```

## Sources

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

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