dbcve.org
CatosOperating system · Cisco

CVE-2007-5651

HIGH · 7.1 CVSS v2.0 Published 2007-10-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
Unspecified vulnerability in the Extensible Authentication Protocol (EAP) implementation in Cisco IOS 12.3 and 12.4 on Cisco Access Points and 1310 Wireless Bridges (Wireless EAP devices), IOS 12.1 and 12.2 on Cisco switches (Wired EAP devices), and CatOS 6.x through 8.x on Cisco switches allows remote attackers to cause a denial of service (device reload) via a crafted EAP Response Identity 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

A vulnerability in Cisco's Extensible Authentication Protocol (EAP) implementation across IOS 12.1-12.4 and CatOS 6.x-8.x allows remote attackers to cause device reload (denial of service) by sending specially crafted EAP Response Identity packets. The flaw affects both wireless devices (Access Points, 1310 Wireless Bridges) and wired switches.

MitigationApply Cisco security patches for this vulnerability to affected IOS and CatOS versions. If patches are unavailable, implement network access control and consider isolating affected devices or disabling EAP where not required.

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
CatosOperating system
Affected:= 6.1= 6.2= 6.3= 6.4= 7.1= 7.2= 7.3= 7.4= 7.5= 7.6= 8.1= 8.2
iOSOperating system
Affected:= 12.1= 12.2= 12.3ja= 12.3jea= 12.3jeb= 12.3jec= 12.4ja

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 checks

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

  1. Identify device OS version
    For Cisco IOS, run 'show version' and look for the IOS release number (e.g., 12.4, 12.3). For CatOS, run 'show version' and note the CatOS version (e.g., 8.1, 7.4).
    Affected if The version matches any of these: CatOS 6.1-8.2, or IOS 12.1-12.4ja (specifically 12.1, 12.2, 12.3ja, 12.3jea, 12.3jeb, 12.3jec, 12.4ja)
  2. Check if EAP is enabled
    On IOS, run 'show running-config | include eap' or 'show dot1x' to see if 802.1X/EAP authentication is configured. On CatOS, run 'show authentication' or 'show dot1x' to check EAP status.
    Affected if EAP-based authentication (802.1X) is enabled on the device
  3. Identify device type
    Check if the device is an Access Point, Wireless Bridge (such as 1310), or a wired switch. Run 'show inventory' or check the device model from 'show version'.
    Affected if The device is an Access Point, 1310 Wireless Bridge, or a wired switch running the affected IOS/CatOS versions with EAP enabled

A device is affected if it runs a vulnerable CatOS (6.1-8.2) or IOS (12.1-12.4ja) version AND has EAP/802.1X authentication enabled, as the attack requires EAP to be configured to process the specially crafted EAP Response Identity packets.

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

Apply Cisco security patches for this vulnerability to affected IOS and CatOS versions. If patches are unavailable, implement network access control and consider isolating affected devices or disabling EAP where not required.

Fix this in Catos Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-5651 — 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-2007-5651 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