Firewall Services ModuleHardware / appliance · Cisco
CVE-2007-5570
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 Firewall Services Module (FWSM) 3.2(1), and 3.1(5) and earlier, allows remote attackers to cause a denial of service (device reload) via a crafted HTTPS request, aka CSCsi77844.
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 confidenceA denial of service vulnerability exists in Cisco Firewall Services Module (FWSM) versions 3.2(1), 3.1(5) and earlier where specially crafted HTTPS requests can cause the device to reload, resulting in service disruption.
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 ModuleHardware / appliance
>= 3.1, <= 3.1\(5\)>= 3.2, <= 3.2\(1\)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
- 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.
-
Confirm the device is a Cisco FWSMIdentify the hardware platform and verify it is running the Cisco Firewall Services Module. On the Catalyst switch or router chassis, use 'show module' or similar commands to list FWSM presence.Affected if The device is not a Cisco FWSM, this CVE does not apply.
-
Determine the installed FWSM versionFrom the FWSM command line, execute 'show version' or 'show module' to display the FWSM software version number.Affected if The installed version falls within 3.1.x through 3.1(5) or 3.2.x through 3.2(1), indicating the device is in the affected version range.
-
Check if HTTPS traffic handling is enabledExamine the FWSM configuration for HTTPS inspection, inspection rules, or policy maps that process HTTPS traffic. Use 'show running-config' and search for 'https', 'inspect', or 'inspection' related policies.Affected if HTTPS inspection or handling is not configured, the vulnerability is not reachable through this feature.
-
Verify network exposure to HTTPS trafficReview access-lists and interface configurations to determine if HTTPS traffic from untrusted networks can reach the FWSM. Check inbound ACLs applied to interfaces that permit HTTPS (port 443) traffic.Affected if HTTPS traffic from untrusted sources is permitted to reach the FWSM, the device is vulnerable to the specially crafted requests described in the CVE.
The environment is affected if the device is a Cisco FWSM running version 3.1 through 3.1(5) or 3.2 through 3.2(1), with HTTPS traffic inspection or handling enabled, and exposed to potentially malicious HTTPS requests 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 FWSM to a patched version beyond 3.2(1)/3.1(5), or implement network-level access controls to restrict HTTPS traffic to trusted sources.
Fix this in Firewall Services Module
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-5570 — 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-2007-5570 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