WebnsApplication · Cisco
CVE-2007-4654
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 · uneditedUnspecified vulnerability in SSHield 1.6.1 with OpenSSH 3.0.2p1 on Cisco WebNS 8.20.0.1 on Cisco Content Services Switch (CSS) series 11000 devices allows remote attackers to cause a denial of service (connection slot exhaustion and device crash) via a series of large packets designed to exploit the SSH CRC32 attack detection overflow (CVE-2001-0144), possibly a related issue to CVE-2002-1024.
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 confidenceThis CVE describes a denial of service vulnerability in SSHield 1.6.1 with OpenSSH 3.0.2p1 running on Cisco WebNS 8.20.0.1 for the Cisco CSS 11000 series content switch. Remote attackers can cause connection slot exhaustion and device crash by sending a series of large packets that exploit the SSH CRC32 attack detection overflow mechanism (originally CVE-2001-0144).
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
WebnsApplication
= 8.20.0.1= 3.0.2p1= 1.6.1CVSS 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
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
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 the Cisco CSS 11000 device and its firmware versionAccess the device console or management interface and run the 'show version' command to confirm the device model is CSS 11000 series and note the WebNS firmware versionAffected if The device is a Cisco CSS 11000 series running Cisco WebNS version 8.20.0.1
-
Verify the OpenSSH version running on the deviceConnect to the device via SSH or console and check the SSH daemon version using 'sshd -v' or checking the banner when connecting from an external systemAffected if OpenSSH version 3.0.2p1 is installed and running
-
Confirm SSHield 1.6.1 is installedCheck for the presence of SSHield on the system using 'show module' or checking system files for the SSHield version stringAffected if Teamf1 SSHield version 1.6.1 is installed and active
-
Verify SSH service is enabled and accessibleConfirm SSH is listening on the device by attempting a connection or checking with 'show service ssh' from the device consoleAffected if SSH service is enabled and accessible on the device
A system is affected if it is a Cisco CSS 11000 running WebNS 8.20.0.1 with OpenSSH 3.0.2p1 and SSHield 1.6.1, where SSH service is enabled and exposed to network 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 dataGiven the legacy nature of Cisco CSS 11000 hardware (End-of-Life), primary mitigation involves network-level controls such as rate limiting SSH connections at upstream firewalls or implementing ACLs to restrict SSH access to trusted sources, as software updates are unlikely available for this deprecated platform.
Fix this in Webns
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-4654 — 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-4654 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