Adaptive Security Appliance SoftwareOperating system · Cisco
CVE-2015-0675
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 failover ipsec implementation in Cisco Adaptive Security Appliance (ASA) Software 9.1 before 9.1(6), 9.2 before 9.2(3.3), and 9.3 before 9.3(3) does not properly validate failover communication messages, which allows remote attackers to reconfigure an ASA device, and consequently obtain administrative control, by sending crafted UDP packets over the local network to the failover interface, aka Bug ID CSCur21069.
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 failover ipsec implementation in Cisco ASA Software versions 9.1 before 9.1(6), 9.2 before 9.2(3.3), and 9.3 before 9.3(3) lacks proper validation of failover communication messages. Remote attackers on the local network can send crafted UDP packets to the failover interface to reconfigure the ASA device and gain administrative control.
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
= 9.1.1= 9.1.1.4= 9.1.2= 9.1.2.8= 9.1.3= 9.1.3.2= 9.1.4= 9.1.4.5= 9.1.5= 9.1.5.10= 9.1.5.12= 9.1.5.15CVSS 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
- Adjacent
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:A/AC:L/Au:N/C:C/I:C/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 running ASA software versionExecute 'show version' on the ASA CLI and locate the version string (e.g., 9.1(5)15)Affected if The version falls before 9.1(6), 9.2(3.3), or 9.3(3)
-
Verify if failover feature is enabledExecute 'show failover' and check for active failover statusAffected if Failover state shows as Active/Standby or Active/Active with failover configured
-
Confirm ipsec failover is configuredExecute 'show running-config failover' and look for 'ipsec' keyword in the failover configurationAffected if The output contains ipsec failover configuration lines
-
Identify the failover interface configurationExecute 'show interface' and locate the failover interface (typically 'failover' or 'GigabitEthernet0/2' with 'failover' keyword)Affected if A dedicated failover interface is defined and operational
-
Check failover interface network accessibilityReview the network topology or ACLs controlling access to the failover interface IP addressAffected if The failover interface IP is reachable from untrusted network segments
The environment is affected if the ASA runs a vulnerable version (before 9.1(6), 9.2(3.3), or 9.3(3)) AND has ipsec failover enabled with the failover interface exposed to untrusted networks.
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 dataUpgrade Cisco ASA Software to version 9.1(6), 9.2(3.3), 9.3(3) or later. Additionally, restrict access to the failover interface by placing it in a dedicated management VLAN or using ACLs to limit which systems can communicate with it.
Fix this in Adaptive Security Appliance Software
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing4.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0675 — 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-0675 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