CatalystHardware / appliance · Cisco

CVE-2005-1942

HIGH · 7.5 CVSS v2.0 Published 2005-06-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/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
Cisco switches that support 802.1x security allow remote attackers to bypass port security and gain access to the VLAN via spoofed Cisco Discovery Protocol (CDP) messages.

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

Cisco switches with 802.1x port security can be bypassed by remote attackers sending spoofed Cisco Discovery Protocol (CDP) messages. The attack allows unauthorized access to the VLAN by tricking the switch into trusting fraudulent CDP advertisements, circumventing the 802.1x authentication controls.

MitigationUpgrade Cisco switch firmware to versions that address CDP spoofing vulnerabilities, or disable CDP on untrusted ports if not required, and implement additional VLAN access controls.

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
CatalystHardware / appliance
Affected:all versions

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
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/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. Confirm Cisco Catalyst switch model and firmware version
    Use 'show version' command on the switch CLI to identify the switch model and running IOS version
    Affected if The device is a Cisco Catalyst switch running any firmware version - all versions are affected per CVE scope
  2. Verify 802.1x port-based authentication is configured
    Use 'show dot1x all' or 'show running-config | include dot1x' to check if 802.1x is enabled on any ports
    Affected if 802.1x authentication is actively configured on switch ports - this is the security control being bypassed
  3. Check CDP protocol status on switch ports
    Use 'show cdp neighbors' and 'show cdp interface' to see if CDP is globally enabled or running on specific ports
    Affected if CDP is enabled on ports, especially on access ports where untrusted devices connect - this is the attack vector
  4. Identify ports with both 802.1x and CDP simultaneously enabled
    Cross-reference 'show dot1x interface' output with 'show cdp interface' output per port to find ports running both protocols
    Affected if Ports have both 802.1x authentication AND CDP enabled - creating the condition where CDP spoofing can bypass 802.1x
  5. Check for CDP packet filtering or port security settings
    Use 'show run interface [interface-id]' to inspect per-port CDP configuration and any access control settings
    Affected if CDP packets are permitted on ports without additional filtering or validation - the switch trusts CDP advertisements without verification

A Cisco Catalyst switch is affected if it has 802.1x authentication enabled concurrently with CDP protocol running on the same ports, allowing attackers to spoof CDP messages to bypass 802.1x VLAN access controls.

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 Cisco switch firmware to versions that address CDP spoofing vulnerabilities, or disable CDP on untrusted ports if not required, and implement additional VLAN access controls.

Fix this in Catalyst 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-2005-1942 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2005-1942 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