Firewall Services Module SoftwarePlugin / extension · Cisco
CVE-2014-0710
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 · uneditedRace condition in the cut-through proxy feature in Cisco Firewall Services Module (FWSM) Software 3.x before 3.2(28) and 4.x before 4.1(15) allows remote attackers to cause a denial of service (device reload) via certain matching traffic, aka Bug ID CSCuj16824.
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 confidenceRace condition vulnerability in the cut-through proxy feature of Cisco FWSM Software allows remote attackers to cause denial of service via device reload by sending certain matching traffic. Affects versions 3.x before 3.2(28) and 4.x before 4.1(15).
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
Firewall Services Module SoftwarePlugin / extension
= 3.1= 3.1\(2\)= 3.1\(3\)= 3.1\(4\)= 3.1\(5\)= 3.1\(6\)= 3.1\(7\)= 3.1\(8\)= 3.1\(9\)= 3.1\(10\)= 3.1\(11\)= 3.1\(12\)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 Cisco FWSM deviceLog into the parent Cisco switch or router and run 'show module' or 'show chassis' to confirm the Firewall Services Module is presentAffected if The device is not a Cisco FWSM module (this CVE does not apply)
-
Get FWSM software versionFrom the switch/router console, execute 'show module <slot> details' or connect to the FWSM and run 'show version' to retrieve the installed software versionAffected if Version begins with 3.x and is below 3.2(28), or begins with 4.x and is below 4.1(15)
-
Check cut-through proxy configurationFrom FWSM exec mode, run 'show running-config' and search for 'cut-through' or 'cut-through proxy' configuration statements. Also check 'show service-policy' for cut-through proxy policy assignmentsAffected if Cut-through proxy feature is explicitly configured and active on any interface
-
Verify traffic matching for cut-through proxyReview 'show conn' output and access-lists to identify traffic flows that match any configured cut-through proxy policies. Run 'show service-policy interface <name>' to see active cut-through proxy service policiesAffected if Cut-through proxy policies are applied to interfaces and matching traffic flows exist
The environment is affected only if the device is a Cisco FWSM running version 3.x before 3.2(28) or 4.x before 4.1(15) AND the cut-through proxy feature is actively configured and processing traffic.
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 FWSM Software to version 3.2(28) or later for 3.x branches, or 4.1(15) or later for 4.x branches to patch the race condition vulnerability.
Fix this in Firewall Services Module Software
Scoped from the published advisory
- Consultation3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0710 — 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-2014-0710 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