dbcve.org
Unified CallmanagerApplication · Cisco

CVE-2008-3800

HIGH · 7.1 CVSS v2.0 Published 2008-09-26
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
Unspecified vulnerability in the Session Initiation Protocol (SIP) implementation in Cisco IOS 12.2 through 12.4 and Unified Communications Manager 4.1 through 6.1, when VoIP is configured, allows remote attackers to cause a denial of service (device or process reload) via unspecified valid SIP messages, aka Cisco Bug ID CSCsu38644, a different vulnerability than CVE-2008-3801 and CVE-2008-3802.

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 confidence

A denial of service vulnerability in Cisco IOS 12.2-12.4 and Unified Communications Manager 4.1-6.1 when VoIP is configured. The SIP (Session Initiation Protocol) implementation fails to properly handle certain valid SIP messages, causing the device or Cisco Unified Communications Manager process to reload. The vulnerability is remotely exploitable without authentication.

MitigationApply Cisco security updates for the relevant IOS version and Unified Communications Manager version. If patching is not immediately possible, consider disabling SIP services if not required, or implement SIP traffic rate limiting and network segmentation to reduce attack surface.

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
Unified CallmanagerApplication
Affected:= 4.1= 4.2= 4.3
Unified Communications ManagerApplication
Affected:= 4.1= 5.0= 5.1= 6.1
iOSOperating system
Affected:= 12.2= 12.3= 12.4

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. Check Cisco IOS version
    Execute 'show version' on the IOS device and locate the version number in the output (typically shown as something like 12.2(XX), 12.3(XX), or 12.4(XX))
    Affected if The IOS version starts with 12.2, 12.3, or 12.4 (any subversion) and VoIP/SIP is configured
  2. Check Cisco Unified Communications Manager version
    On the CUCM server, run 'utils system version' from the CLI or check the About page in the administration interface for the version number
    Affected if The CUCM/Unified CallManager version is 4.1, 4.2, 4.3, 5.0, 5.1, or 6.1 and SIP is enabled
  3. Verify SIP protocol is enabled on IOS
    Execute 'show running-config | include sip' or 'show voip sip' to examine the SIP configuration in the IOS running config
    Affected if SIP-related configuration lines appear (such as 'sip', 'voip', 'sip-ua', or SIP gateway settings)
  4. Verify SIP is enabled on Unified Communications Manager
    Log into the CUCM Administration interface, navigate to System > Service Parameters, and check if the Cisco SIP Proxy service is active, or use 'show process' to confirm SIP processes are running
    Affected if The SIP Proxy service or related SIP processes are running on the CUCM server

The environment is affected if either Cisco IOS version 12.2/12.3/12.4 or CUCM version 4.1-6.1 is in use AND SIP/VoIP functionality is enabled.

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 Cisco security updates for the relevant IOS version and Unified Communications Manager version. If patching is not immediately possible, consider disabling SIP services if not required, or implement SIP traffic rate limiting and network segmentation to reduce attack surface.

Fix this in Unified Callmanager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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