Cisco IosOperating system · Cisco
CVE-2009-0634
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 · uneditedMultiple unspecified vulnerabilities in the home agent (HA) implementation in the (1) Mobile IP NAT Traversal feature and (2) Mobile IPv6 subsystem in Cisco IOS 12.3 through 12.4 allow remote attackers to cause a denial of service (input queue wedge and interface outage) via an ICMP packet, aka Bug ID CSCso05337.
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 confidenceThis CVE affects Cisco IOS 12.3-12.4 and involves unspecified vulnerabilities in the Mobile IP NAT Traversal feature and Mobile IPv6 subsystem within the Home Agent implementation. Remote attackers can send specially crafted ICMP packets to cause a denial of service, resulting in input queue wedge and interface outage.
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
Cisco IosOperating system
= 12.3= 12.4CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Cisco IOS versionRun 'show version' and look for the IOS version number in the output. Look for lines showing 'IOS (tm)...' or 'Version 12.3' or 'Version 12.4'Affected if The version displayed is exactly 12.3 or 12.4 (or falls within the 12.3-12.4 range)
-
Verify Mobile IP Home Agent is enabledRun 'show running-config | include mobile ip' or 'show ip mobile home-agent' to check if the Mobile IP Home Agent feature is configuredAffected if Mobile IP Home Agent is actively enabled and running
-
Check Mobile IPv6 subsystem statusRun 'show ipv6 mobile' or check running configuration for 'ipv6 mobile' commands to see if Mobile IPv6 is configuredAffected if Mobile IPv6 subsystem is configured or enabled
-
Confirm NAT Traversal for Mobile IPRun 'show ip mobile nat-traversal' or check running configuration for 'mobile ip nat traversal' statementsAffected if NAT Traversal for Mobile IP is enabled on the device
A device is affected if it runs Cisco IOS version 12.3 or 12.4 AND has Mobile IP Home Agent, Mobile IPv6, or NAT Traversal features enabled, making it vulnerable to specially crafted ICMP packets causing denial of service.
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 dataUpgrade affected Cisco IOS devices to a patched version beyond 12.4. If immediate patching is not possible, consider filtering ICMP traffic to the Mobile IP home agent interfaces as a compensating control, though this may impact legitimate mobile node communications.
Fix this in Cisco Ios
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-0634 — 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-2009-0634 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