Adaptive Security Appliance SoftwareApplication · Cisco
CVE-2013-5568
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 auto-update implementation in Cisco Adaptive Security Appliance (ASA) Software 9.0.3.6 and earlier allows remote attackers to cause a denial of service (device reload) via crafted update data, aka Bug ID CSCui33308.
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 auto-update mechanism in Cisco ASA Software versions 9.0.3.6 and earlier fails to properly validate incoming update data. Remote attackers can send specially crafted update packets that trigger an unrecoverable device reload, causing 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.0.3\(6\)= 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
- M
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Complete
AV:N/AC:M/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 ASA software versionRun 'show version' command on the Cisco ASA device and locate the software version in the outputAffected if The displayed version is 9.0.3(6) or earlier, or matches any of these: 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)
-
Verify auto-update feature statusRun 'show running-config | include auto-update' or 'show auto-update' to see if the auto-update feature is configuredAffected if The auto-update feature is enabled and configured with a remote server or polling settings
-
Check auto-update server configurationRun 'show running-config | include update' to display any configured update servers or URLsAffected if An auto-update server URL or IP address is configured, indicating the device attempts to receive updates from the network
-
Confirm management interface exposureReview the auto-update configuration for the source interface and verify network accessibility from untrusted networksAffected if The auto-update interface is reachable from networks outside the administrative perimeter
-
Check for recent unexpected reloadsReview logs with 'show log' or 'show crashinfo' for patterns of unexplained device reloads or crashesAffected if The device has experienced unrecoverable reloads without corresponding administrative cause or logged errors
A Cisco ASA device is affected if it runs version 9.0.3(6) or earlier (or a listed 7.0.x version) AND has the auto-update feature enabled with network exposure to potential attackers.
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 dataUpdate Cisco ASA Software to a version newer than 9.0.3.6. If immediate patching is not feasible, disable the auto-update feature and apply updates manually during scheduled maintenance windows.
Fix this in Adaptive Security Appliance Software
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-5568 — 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-5568 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