dbcve.org
Ios Transmission Control ProtocolHardware / appliance · Cisco

CVE-2007-0481

HIGH · 7.8 CVSS v2.0 Published 2007-01-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/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 IOS allows remote attackers to cause a denial of service (crash) via a crafted IPv6 Type 0 Routing header.

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

This CVE targets Cisco IOS devices where a crafted IPv6 packet containing a Type 0 Routing header can cause the device to crash. The vulnerability exists in the IPv6 packet processing code, where the malformed routing header triggers a fatal error resulting in a denial of service.

MitigationApply the appropriate Cisco IOS security update/patch for this vulnerability, or disable IPv6 processing on affected devices if patching is not immediately feasible.

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
Ios Transmission Control ProtocolHardware / appliance
Affected:= 12= 12.0da= 12.0db= 12.0dc= 12.0s= 12.0sc= 12.0sl= 12.0sp= 12.0st= 12.0sx= 12.0sy= 12.0sz

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 checks

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

  1. Identify the Cisco IOS version
    Execute 'show version' on the device CLI to retrieve the installed IOS version number
    Affected if The version matches any of these: 12.0, 12.0da, 12.0db, 12.0dc, 12.0s, 12.0sc, 12.0sl, 12.0sp, 12.0st, 12.0sx, 12.0sy, 12.0sz
  2. Confirm IPv6 is enabled on the device
    Execute 'show ipv6 interface' or check the configuration with 'show running-config | include ipv6'
    Affected if IPv6 interfaces are configured or 'ipv6 unicast-routing' is present in the configuration
  3. Check for IPv6 routing header processing
    Review the device configuration for any IPv6 routing header settings using 'show running-config | include routing' in IPv6 context
    Affected if IPv6 routing header processing is enabled and the device handles IPv6 traffic

A device is affected if it runs one of the listed 12.0.x IOS versions AND has IPv6 processing enabled, making it vulnerable to crashes from crafted Type 0 Routing header 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 the appropriate Cisco IOS security update/patch for this vulnerability, or disable IPv6 processing on affected devices if patching is not immediately feasible.

Fix this in Ios Transmission Control Protocol Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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