Adaptive Security Appliance SoftwareApplication · Cisco
CVE-2013-5567
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 · uneditedCisco Adaptive Security Appliance (ASA) Software 8.4(.6) and earlier, when using an unsupported configuration with overlapping criteria for filtering and inspection, allows remote attackers to cause a denial of service (traffic loop and device crash) via a packet that triggers multiple matches, aka Bug ID CSCui45606.
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 confidenceCisco ASA Software 8.4(.6) and earlier contains a vulnerability where an unsupported configuration with overlapping criteria for filtering and inspection causes a traffic loop and device crash when a packet triggers multiple matches, leading to 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
<= 8.4\(6\)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.
-
Check ASA software versionRun 'show version' on the Cisco ASA command line interface and locate the software version in the output. Compare the installed version against the affected range: 8.4(6) and earlier.Affected if The device runs Cisco ASA Software version 8.4(6) or earlier
-
Identify packet filtering rulesRun 'show run access-list' or similar command to list all configured access control lists and filtering rules on the ASA device.Affected if Multiple packet filtering rules are configured on the device
-
Identify inspection rulesRun 'show run | include inspect' to display all configured inspection policies (such as HTTP, FTP, or DNS inspection).Affected if Inspection rules are enabled on the device
-
Detect overlapping rule criteriaReview the output from both the filtering and inspection rule checks. Identify any configurations where the same traffic could match both a filter rule and an inspection rule simultaneously.Affected if There are filter and inspection rules with overlapping match criteria that could process the same packet
The environment is affected if the Cisco ASA runs version 8.4(6) or earlier AND has overlapping filter and inspection rules that could cause a traffic loop when a packet triggers multiple matches.
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 dataAvoid using overlapping filter and inspection rules on affected ASA devices. Update to a patched Cisco ASA software version. Review existing rule configurations for overlapping criteria.
Fix this in Adaptive Security Appliance Software
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-5567 — 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-5567 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