dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 3 Dec 2024.
Adaptive Security Appliance SoftwareOperating system · Cisco

CVE-2014-2120

MEDIUM · 6.1 CVSS v3.1 Published 2014-03-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
In the wild 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
Cross-site scripting (XSS) vulnerability in the WebVPN login page in Cisco Adaptive Security Appliance (ASA) Software allows remote attackers to inject arbitrary web script or HTML via an unspecified parameter, aka Bug ID CSCun19025.

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 confidence

Cross-site scripting (XSS) vulnerability in the Cisco ASA WebVPN login page allows remote attackers to inject arbitrary JavaScript or HTML through an unspecified parameter. This stored XSS executes in the browsers of users accessing the WebVPN portal, potentially enabling session hijacking or credential theft.

MitigationApply the relevant Cisco ASA security update or patch for this vulnerability. Until patches can be deployed, consider implementing input validation at upstream network devices or restricting WebVPN access to trusted networks.

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:all versions

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 if Cisco ASA with WebVPN is deployed
    Query your asset inventory or network diagrams for Cisco Adaptive Security Appliance devices that have WebVPN feature enabled. Check ASA configuration with command: show vpn-sessiondb webvpn
    Affected if No Cisco ASA with WebVPN found - not affected; ASA with WebVPN enabled - potentially affected
  2. Confirm WebVPN is active on the ASA
    Run 'show vpn-sessiondb webvpn' or 'show webvpn' on the ASA CLI to see if WebVPN sessions or configuration exist
    Affected if No WebVPN sessions or configuration present - not affected; WebVPN is configured and active - potentially affected
  3. Check ASA software version
    Run 'show version' on the ASA CLI and note the software version number. Compare against Cisco's official advisory for CVE-2014-2120
    Affected if Version is documented as affected in Cisco advisory - affected
  4. Inspect WebVPN login page for reflected parameters
    Access the WebVPN login page externally (or internally if testing) and examine HTML source. Look for any URL parameters that might be reflected in the login page without proper sanitization
    Affected if Parameters are reflected unsanitized in login page HTML - confirmed affected

If a Cisco ASA with WebVPN enabled is deployed, the environment is likely affected since all versions of Cisco ASA Software are vulnerable to this XSS in the WebVPN login page.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the relevant Cisco ASA security update or patch for this vulnerability. Until patches can be deployed, consider implementing input validation at upstream network devices or restricting WebVPN access to trusted networks.

Recommended fix Moderate confidence

Cisco ASA Software version containing fix for CSCun19025 (consult Cisco Security Advisory for specific release)

  1. Check Cisco Security Advisories for CVE-2014-2120 to identify the specific fixed ASA software version
  2. Identify your current ASA software version using 'show version' command
  3. Review Cisco's ASA software release notes for versions containing the fix for CSCun19025
  4. Download the recommended fixed ASA software version from Cisco
  5. Plan maintenance window and backup current ASA configuration using 'write net' or 'copy running-config startup-config'
  6. Upgrade ASA software following Cisco's upgrade procedure documentation
  7. Verify the upgrade was successful and the WebVPN login page is functioning correctly
  8. Confirm the XSS vulnerability is remediated by testing the WebVPN login with the specific injection vector
Caveat Review Cisco ASA release notes for any compatibility concerns or configuration changes required when upgrading to the fixed version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Adaptive Security Appliance Software Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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