dbcve.org
iOSOperating system · Cisco

CVE-2009-0630

HIGH · 7.1 CVSS v2.0 Published 2009-03-27
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
The (1) Cisco Unified Communications Manager Express; (2) SIP Gateway Signaling Support Over Transport Layer Security (TLS) Transport; (3) Secure Signaling and Media Encryption; (4) Blocks Extensible Exchange Protocol (BEEP); (5) Network Admission Control HTTP Authentication Proxy; (6) Per-user URL Redirect for EAPoUDP, Dot1x, and MAC Authentication Bypass; (7) Distributed Director with HTTP Redirects; and (8) TCP DNS features in Cisco IOS 12.0 through 12.4 do not properly handle IP sockets, which allows remote attackers to cause a denial of service (outage or resource consumption) via a series of crafted TCP packets.

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

Multiple Cisco IOS 12.0-12.4 features including SIP Gateway TLS, Secure Signaling, BEEP, NAC HTTP Authentication Proxy, and TCP DNS do not properly handle IP sockets, allowing remote attackers to cause denial of service via crafted TCP packets.

MitigationUpgrade affected Cisco IOS devices from versions 12.0-12.4 to a patched version; apply Cisco security advisories and ensure proper network segmentation to limit exposure to unauthenticated attackers.

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
iOSOperating system
Affected:= 12.0= 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
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. Determine Cisco IOS version
    Run 'show version' command on the IOS device to obtain the installed IOS version number
    Affected if The version displayed falls within 12.0 through 12.4 (including variants like 12.0da, 12.0s, 12.0sy, etc.)
  2. Check if SIP Gateway with TLS is enabled
    Run 'show running-config | include sip' and look for 'sip' configuration; check for 'transport tls' or 'transport tcp tls' under sip gateway configuration
    Affected if SIP Gateway TLS transport is configured and the IOS version is vulnerable
  3. Check if Secure Signaling is enabled
    Run 'show running-config | include secure' to look for secure signaling configurations such as 'secure signaling' or SRTP/SRTCP settings
    Affected if Secure Signaling feature is configured and the IOS version is vulnerable
  4. Check if BEEP (Blocks Extensible Exchange Protocol) is enabled
    Run 'show running-config | include beep' to look for BEEP-related configuration statements
    Affected if BEEP is configured and the IOS version is vulnerable
  5. Check if NAC HTTP Authentication Proxy is enabled
    Run 'show running-config | include ip admission' or 'show running-config | include aaa authorization' to look for NAC or HTTP proxy authentication configurations
    Affected if NAC HTTP Authentication Proxy is configured and the IOS version is vulnerable
  6. Check if TCP DNS is enabled
    Run 'show running-config | include ip name-server' or check for 'ip dns' configurations; verify if TCP-based DNS is permitted
    Affected if TCP DNS service is enabled and the IOS version is vulnerable

The device is affected if it runs Cisco IOS version 12.0-12.4 and has any of the vulnerable features (SIP Gateway TLS, Secure Signaling, BEEP, NAC HTTP Authentication Proxy, or TCP DNS) enabled and exposed to network traffic.

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 affected Cisco IOS devices from versions 12.0-12.4 to a patched version; apply Cisco security advisories and ensure proper network segmentation to limit exposure to unauthenticated attackers.

Fix this in iOS 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-2009-0630 — 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-2009-0630 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