Adaptive Security Appliance SoftwareApplication · Cisco
CVE-2013-5560
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 IPv6 implementation in Cisco Adaptive Security Appliance (ASA) Software 9.1.3 and earlier, when NAT64 or NAT66 is enabled, does not properly process NAT rules, which allows remote attackers to cause a denial of service (device reload) via crafted packets, aka Bug ID CSCue34342.
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 IPv6 implementation in Cisco ASA Software 9.1.3 and earlier contains a flaw in NAT rule processing when NAT64 or NAT66 is enabled. Remote attackers can send crafted IPv6 packets that trigger improper NAT handling, causing the ASA device to reload and 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 SoftwareApplication
<= 9.1\(3\)= 7.0= 7.0\(0\)= 7.0\(1\)= 7.0\(2\)= 7.0\(4\)= 7.0\(5\)= 7.0\(5.2\)= 7.0\(6\)= 7.0\(6.7\)= 7.0\(7\)= 7.0\(8\)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
- High
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Complete
AV:N/AC:H/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.
-
Identify the Cisco ASA device and software versionRun the command 'show version' on the ASA CLI to display the installed Cisco ASA Software version numberAffected if The displayed version is 9.1(3) or earlier, OR is 7.0, 7.0(0), 7.0(1), 7.0(2), 7.0(4), 7.0(5), 7.0(5.2), 7.0(6), 7.0(6.7), 7.0(7), or 7.0(8)
-
Confirm NAT64 feature is enabledRun 'show running-config nat' or 'show nat detail' to inspect NAT64 translation rules configured on the deviceAffected if Any active NAT64 rule or translation entry is present in the configuration
-
Confirm NAT66 feature is enabledRun 'show running-config nat' or 'show nat detail' and look for NAT66-specific translation rulesAffected if Any active NAT66 rule or translation entry is present in the configuration
The device is affected if it runs Cisco ASA Software version 9.1(3) or earlier (or the listed 7.0.x versions) AND has NAT64 or NAT66 translation rules actively configured.
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 a version later than 9.1.3. If immediate patching is not feasible, disable NAT64/NAT66 features if not required, and implement network-based filtering to restrict crafted packet sources.
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
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 locallyCheck whether your project pulls in CVE-2013-5560 — 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-2013-5560 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