dbcve.org
Adaptive Security Appliance SoftwareOperating system · Cisco

CVE-2014-2128

MEDIUM · 5.0 CVSS v2.0 Published 2014-04-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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
The SSL VPN implementation in Cisco Adaptive Security Appliance (ASA) Software 8.2 before 8.2(5.47, 8.3 before 8.3(2.40), 8.4 before 8.4(7.3), 8.6 before 8.6(1.13), 9.0 before 9.0(3.8), and 9.1 before 9.1(3.2) allows remote attackers to bypass authentication via (1) a crafted cookie value within modified HTTP POST data or (2) a crafted URL, aka Bug ID CSCua85555.

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

The vulnerability allows remote attackers to bypass authentication on Cisco ASA SSL VPN by using either a crafted cookie value in modified HTTP POST data or a crafted URL. This enables unauthenticated remote attackers to gain unauthorized access to the SSL VPN without valid credentials.

MitigationUpgrade Cisco ASA Software to the fixed versions (8.2(5.47), 8.3(2.40), 8.4(7.3), 8.6(1.13), 9.0(3.8), or 9.1(3.2) or later per the Cisco security advisory. Alternatively, ensure VPN access is restricted to known IP ranges via access control lists as a temporary mitigation.

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 SoftwareOperating system
Affected:= 8.2= 8.3\(1\)= 8.4= 8.6= 9.0= 9.1

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
Authentication
None
Confidentiality
Partial
Integrity
None
Availability
None

AV:N/AC:L/Au:N/C:P/I:N/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 Cisco ASA device and obtain software version
    Log into the ASA CLI and run 'show version' to display the running software version. Alternatively, check your asset inventory or configuration management system if Cisco ASA appliances are managed centrally.
    Affected if The displayed version matches 8.2.x, 8.3.x, 8.4.x, 8.6.x, 9.0.x, or 9.1.x (any build within these major.minor branches).
  2. Determine if SSL VPN (WebVPN) is enabled
    From the ASA CLI, run 'show vpn-sessiondb' or 'show webvpn' to check for active or configured SSL VPN sessions. Also review the running configuration with 'show running-config' and look for 'webvpn' or 'ssl vpn' entries.
    Affected if SSL VPN or WebVPN is enabled and configured on any interface.
  3. Verify network exposure of the SSL VPN interface
    Review the ASA interface configuration using 'show interface' and examine access-list configurations. Determine whether the outside or untrusted interface accepts HTTPS connections to the VPN portal.
    Affected if The SSL VPN portal is accessible from an untrusted or external network (such as the internet) without IP-based restrictions.

You are affected if your Cisco ASA runs any 8.2.x, 8.3.x, 8.4.x, 8.6.x, 9.0.x, or 9.1.x software version AND has SSL VPN enabled AND is exposed to untrusted networks.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Cisco ASA Software to the fixed versions (8.2(5.47), 8.3(2.40), 8.4(7.3), 8.6(1.13), 9.0(3.8), or 9.1(3.2) or later per the Cisco security advisory. Alternatively, ensure VPN access is restricted to known IP ranges via access control lists as a temporary mitigation.

Fix this in Adaptive Security Appliance Software Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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