CVE-2010-4673
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 Appliances (ASA) 5500 series devices with software 8.2(4) and earlier allow remote attackers to cause a denial of service via a flood of packets, aka Bug ID CSCtg06316.
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 confidenceRemote attackers can cause denial of service on Cisco ASA 5500 series devices running software version 8.2(4) and earlier by sending a flood of packets. The vulnerability results in service disruption due to the device being unable to handle the packet volume.
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<= 8.2\(4\)= 7.0= 7.0\(0\)= 7.0\(2\)= 7.0\(4\)= 7.0\(5\)= 7.0\(5.2\)= 7.0\(6.7\)= 7.0.1= 7.0.1.4= 7.0.2= 7.0.4all versionsall versionsCVSS 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 Cisco ASA software versionLog into the ASA CLI and run the command 'show version' to display the running software version. Alternatively, access ASDM and check the Dashboard or Device Information section for the software version.Affected if The displayed version is 8.2(4) or earlier, or is one of the specific 7.0.x versions listed (7.0, 7.0(0), 7.0(2), 7.0(4), 7.0(5), 7.0(5.2), 7.0(6.7), 7.0.1, 7.0.1.4, 7.0.2, 7.0.4), or is any version of the Cisco 5500 Series ASA hardware.
-
Identify device modelRun 'show version' in the ASA CLI or check the device label/hardware specifications to confirm the model is a Cisco ASA 5500 series appliance.Affected if The device is a Cisco ASA 5500 Series Adaptive Security Appliance or Cisco ASA 5500 running any software version.
-
Verify network exposureReview the ASA interface configurations using 'show run interface' and determine which interfaces are externally accessible. Check if the device has interfaces directly exposed to untrusted networks such as the internet.Affected if Any ASA interface is reachable from untrusted networks and the device is running an affected software version.
-
Check for recent service disruptionReview system logs using 'show log' or access the syslog server for records of unexpected reloads, traffic drops, or CPU spikes that coincide with high traffic volumes from external sources.Affected if The device has experienced unexplained denial of service events while running an affected version.
You are affected if your Cisco ASA 5500 series device runs software version 8.2(4) or earlier, or any 7.0.x version listed, and is exposed to network traffic from untrusted sources.
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 8.2(4) that includes the fix for Bug ID CSCtg06316. Implement rate-limiting or traffic filtering at network perimeter to mitigate packet flood attacks until the upgrade can be completed.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-4673 — 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-2010-4673 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