CVE-2007-4430
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 · uneditedUnspecified vulnerability in Cisco IOS 12.0 through 12.4 allows context-dependent attackers to cause a denial of service (device restart and BGP routing table rebuild) via certain regular expressions in a "show ip bgp regexp" command. NOTE: unauthenticated remote attacks are possible in environments with anonymous telnet and Looking Glass access.
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 · moderate confidenceThis vulnerability in Cisco IOS 12.0-12.4 allows context-dependent attackers to cause denial of service via specially crafted regular expressions in the 'show ip bgp regexp' command, triggering device restart and BGP routing table rebuild.
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 dataall versionsall versions= 12.1= 12.2all versions= 10.0= 10.3= 11.0= 11.1= 11.2= 12.0= 12.1= 12.2= 12.3= 12.4all versions= 2.0= 3.0= 3.1= 3.2= 3.3= 3.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Cisco IOS/IOS XR versionRun 'show version' on the device CLI to obtain the installed IOS version numberAffected if The version falls within 10.x, 11.x, or 12.0-12.4 for iOS, or 2.x-3.x for IOS XR, or matches any version for Cisco Cli, Cbos, Ids (all marked as affected)
-
Verify BGP is enabledRun 'show ip bgp summary' or 'show bgp summary' to check if BGP process is runningAffected if BGP is enabled and configured on the device (the vulnerability triggers via 'show ip bgp regexp' command)
-
Confirm the 'show ip bgp regexp' command is accessibleAttempt to run 'show ip bgp regexp .*' or check if the command is available in the current privilege levelAffected if The command is accessible at the current privilege level (typically privilege level 1 or higher)
-
Check for exposed management interfacesReview configuration for 'line vty', 'line telnet', or 'ip http server' settings; check if telnet or HTTP access is enabled externallyAffected if Anonymous telnet, HTTP, or Looking Glass access is permitted from untrusted networks (enables remote unauthenticated exploitation)
A device is affected if it runs any Cisco iOS version 10.x-12.4 or IOS XR 2.x-3.x (or any version of Cli/Cbos/Ids), has BGP enabled, and has the 'show ip bgp regexp' command accessible, particularly if exposed via telnet or unauthenticated interfaces.
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 Cisco IOS to a patched version beyond 12.4, and disable anonymous telnet and Looking Glass access to prevent unauthenticated remote exploitation.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-4430 — 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-2007-4430 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