Adaptive Security Appliance SoftwareOperating system · Cisco
CVE-2015-0677
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 · uneditedThe XML parser in Cisco Adaptive Security Appliance (ASA) Software 8.4 before 8.4(7.28), 8.6 before 8.6(1.17), 9.0 before 9.0(4.33), 9.1 before 9.1(6), 9.2 before 9.2(3.4), and 9.3 before 9.3(3), when Clientless SSL VPN, AnyConnect SSL VPN, or AnyConnect IKEv2 VPN is used, allows remote attackers to cause a denial of service (VPN outage or device reload) via a crafted XML document, aka Bug ID CSCus95290.
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 confidenceThe XML parser in Cisco ASA Software contains a flaw that can be triggered when Clientless SSL VPN, AnyConnect SSL VPN, or AnyConnect IKEv2 VPN is enabled. A remote attacker can send a crafted XML document that causes the VPN service to fail or forces the device to reload, resulting in denial of service.
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
= 8.4.1= 8.4.1.3= 8.4.1.11= 8.4.2= 8.4.2.1= 8.4.2.8= 8.4.3= 8.4.3.8= 8.4.3.9= 8.4.4= 8.4.4.1= 8.4.4.3CVSS 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
- None
- Integrity
- None
- Availability
- Complete
AV:N/AC:L/Au:N/C:N/I:N/A:C
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 the ASA software versionLog into the ASA CLI and execute 'show version'. Look for the software version number in the output.Affected if The version matches any of these: 8.4.1, 8.4.1.3, 8.4.1.11, 8.4.2, 8.4.2.1, 8.4.2.8, 8.4.3, 8.4.3.8, 8.4.3.9, 8.4.4, 8.4.4.1, or 8.4.4.3
-
Check if Clientless SSL VPN is enabledExecute 'show run webvpn' or examine the running configuration for 'webvpn' or 'clientless' entries.Affected if Clientless SSL VPN is configured and active (any webvpn entry is present in the configuration)
-
Check if AnyConnect SSL VPN is enabledExecute 'show run webvpn' and look for 'anyconnect' entries, or check 'show run ssl' for SSL VPN settings.Affected if AnyConnect SSL VPN is configured (anyconnect keyword appears in the webvpn configuration)
-
Check if AnyConnect IKEv2 VPN is enabledExecute 'show run crypto' and look for IKEv2 configuration, or check the overall configuration for 'ikev2' entries under the crypto section.Affected if AnyConnect IKEv2 VPN is configured (ikev2 configuration is present)
The device is affected if it runs any of the listed versions AND has Clientless SSL VPN, AnyConnect SSL VPN, or AnyConnect IKEv2 VPN enabled, as the XML parser flaw only triggers when these VPN features are active.
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 dataApply the vendor-supplied software updates (8.4(7.28), 8.6(1.17), 9.0(4.33), 9.1(6), 9.2(3.4), 9.3(3) or later). If immediate patching is not feasible, restrict VPN access to trusted sources via ACLs or disable unused VPN features.
Fix this in Adaptive Security Appliance Software
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0677 — 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-2015-0677 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