dbcve.org
Ids Sensor SoftwareApplication · Cisco

CVE-2006-4910

MEDIUM · 5.0 CVSS v2.0 Published 2006-09-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
The web administration interface (mainApp) to Cisco IDS before 4.1(5c), and IPS 5.0 before 5.0(6p1) and 5.1 before 5.1(2) allows remote attackers to cause a denial of service (unresponsive device) via a crafted SSLv2 Client Hello packet.

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 confidence

The web administration interface (mainApp) in Cisco IDS before 4.1(5c) and IPS 5.0 before 5.0(6p1) and 5.1 before 5.1(2) is vulnerable to a denial of service attack. Remote attackers can send a specially crafted SSLv2 Client Hello packet to the mainApp component, causing the device to become unresponsive.

MitigationUpgrade to Cisco IDS 4.1(5c), IPS 5.0(6p1), IPS 5.1(2) or later. If immediate upgrade is not possible, consider restricting access to the web administration interface via network segmentation or firewall rules.

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
Ids Sensor SoftwareApplication
Affected:= 4.1\(5b\)
Ips Sensor SoftwareApplication
Affected:= 5.0\(6\)p1= 5.1\(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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Cisco sensor product type
    Log into the device CLI and run 'show version' or check the product banner to determine if it is an IDS Sensor or IPS Sensor
    Affected if The device is a Cisco IDS Sensor or IPS Sensor - other Cisco products are not affected
  2. Check the installed IDS Sensor version
    Run 'show version' or 'show module' command and note the exact software version number (for example, 4.1(5b))
    Affected if The IDS Sensor version is 4.1(5b) exactly (versions before 4.1(5c) are also likely affected)
  3. Check the installed IPS Sensor version
    Run 'show version' command and note the exact software version (for example, 5.0(6), 5.0(6p1), or 5.1(1))
    Affected if The IPS Sensor version is 5.0(6), 5.0(6p1), or 5.1(1) - versions before 5.0(6p1) or 5.1(2) are affected
  4. Verify the mainApp web admin interface is accessible
    Attempt to access the web administration interface via HTTPS on the management port (typically port 443), or run 'show http' or similar command to check if the web interface is enabled
    Affected if The mainApp web administration interface is enabled and reachable - the vulnerability only triggers when mainApp is active and processing SSL connections
  5. Check SSL/TLS configuration for SSLv2 support
    Review the device SSL configuration (via 'show ssl' or checking the management interface settings) to determine if SSLv2 is accepted or enabled
    Affected if SSLv2 protocol is enabled or accepted by the device - the attack specifically uses SSLv2 Client Hello packets

You are affected if you have a Cisco IDS Sensor at version 4.1(5b) or an IPS Sensor at version 5.0(6), 5.0(6p1), or 5.1(1), with the mainApp web administration interface enabled and SSLv2 accepted.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Cisco IDS 4.1(5c), IPS 5.0(6p1), IPS 5.1(2) or later. If immediate upgrade is not possible, consider restricting access to the web administration interface via network segmentation or firewall rules.

Fix this in Ids Sensor Software Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2006-4910 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2006-4910 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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