dbcve.org
Adaptive Security Appliance SoftwareApplication · Cisco

CVE-2019-1713

HIGH · 8.8 CVSS v3.0 Published 2019-05-03
Fix available
A fix is available. Upgrade to 9.4.4.34 / 9.6.4.25 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 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.

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

Cross-site request forgery (CSRF) vulnerability in Cisco Adaptive Security Appliance web-based management interface. Insufficient CSRF protection allows unauthenticated attackers to trick authenticated users into performing unauthorized actions with the victim's privilege level, including configuration changes, information extraction, or device reload if the user has administrative privileges.

MitigationApply the Cisco security update for CVE-2019-1713 when available; if web-based management is not required, disable it. Consider using two-factor authentication and educating users about malicious links.

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 SoftwareApplication
Affected:< 9.4.4.34>= 9.5, < 9.6.4.25>= 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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Confirm ASA web-based management interface is enabled
    Log into the ASA CLI and run 'show running-config | include http server enable' or check via ASDM under Configuration > Device Management > HTTP/HTTPS. Alternatively, inspect the running config for 'http server enable' or 'http 0.0.0.0 0.0.0.0' entries that enable the web interface.
    Affected if The web-based management interface is enabled (http server enable command present in config)
  2. Determine the installed ASA software version
    From the ASA CLI, run 'show version' and locate the 'Adaptive Security Appliance Software Version' line. Record the full version number including any build numbers.
    Affected if The installed version falls within any of these ranges: < 9.4.4.34, >= 9.5 and < 9.6.4.25, >= 9.7 and < 9.8.4, >= 9.9 and < 9.9.2.50, or >= 9.10 and < 9.10.1.17
  3. Check if HTTP management access is exposed to untrusted networks
    Review the http command configuration from 'show running-config | include http' to see which IP addresses are permitted to access the web interface. Look for overly permissive rules such as 'http 0.0.0.0 0.0.0.0' or ranges that include untrusted networks.
    Affected if The HTTP management interface is accessible from untrusted networks (any IP not restricted to management-only networks)
  4. Verify authentication method for web management
    Check the ASA configuration for authentication settings under the relevant AAA sections, or examine if local authentication or AAA is required for web interface access. Run 'show running-config | include aaa' to view authentication configuration.
    Affected if Web management does not enforce two-factor or strong authentication mechanisms

You are affected if the ASA web-based management interface is enabled AND your installed software version falls within any of the affected version ranges listed.

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 9.4.4.34 / 9.6.4.25 / 9.8.4 or later
Fixed in 9.4.4.349.6.4.259.8.4
Interim mitigation

Apply the Cisco security update for CVE-2019-1713 when available; if web-based management is not required, disable it. Consider using two-factor authentication and educating users about malicious links.

Fix this in Adaptive Security Appliance Software Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-1713 — 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-1713 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