CVE-2019-1705
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 · uneditedA vulnerability in the remote access VPN session manager of Cisco Adaptive Security Appliance (ASA) Software could allow a unauthenticated, remote attacker to cause a denial of service (DoS) condition on the remote access VPN services. The vulnerability is due to an issue with the remote access VPN session manager. An attacker could exploit this vulnerability by requesting an excessive number of remote access VPN sessions. An exploit could allow the attacker to cause a DoS condition.
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 · moderate confidenceA vulnerability in the remote access VPN session manager of Cisco Adaptive Security Appliance (ASA) Software allows an unauthenticated, remote attacker to cause a denial of service by requesting an excessive number of remote access VPN sessions, triggering a resource exhaustion condition in the session manager.
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>= 9.4, < 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.17CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Determine Cisco ASA software versionLog into the ASA CLI and run the command: `show version` or `show version | include Software` to display the installed Cisco ASA Software version.Affected if The displayed version falls within any of these ranges: 9.4.x before 9.4.4.34, 9.5.x before 9.6.4.25, 9.7.x before 9.8.4, 9.9.x before 9.9.2.50, or 9.10.x before 9.10.1.17.
-
Verify remote access VPN is enabledRun the command: `show running-config | include (anyconnect|webvpn|ipsec|remote-access)` or check `show vpn-sessiondb summary` to see if any remote access VPN tunnels are configured or active.Affected if Remote access VPN functionality (AnyConnect, IPsec remote access, or WebVPN) is enabled on the device.
-
Check for existing VPN session limitsRun `show running-config | include rate-limit` or `show resource usage` to see if any rate limiting or resource allocation is configured for VPN sessions.Affected if No rate limiting or resource constraints are imposed on VPN sessions, leaving the session manager vulnerable to exhaustion.
-
Review current VPN session stateRun `show vpn-sessiondb` or `show resource usage` to observe the current number of active remote access VPN sessions and available session capacity.Affected if The device shows high session usage approaching configured limits, or the session manager appears unstable under load.
The device is affected if it runs an ASA software version within the affected ranges listed above AND has remote access VPN enabled, regardless of current session load.
Generated from the published advisory. Verify against your own configuration.
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 data9.4.4.349.6.4.259.8.4
Apply the Cisco software patch for CVE-2019-1705. Implement rate limiting on VPN connections as a compensating control if immediate patching is not feasible.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1705 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-1705 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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