Unified CallmanagerApplication · Cisco
CVE-2008-3801
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 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 CSCsm46064, a different vulnerability than CVE-2008-3800 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 confidenceThis is a denial-of-service vulnerability in Cisco's Session Initiation Protocol (SIP) implementation affecting IOS 12.2-12.4 and Unified Communications Manager 4.1-6.1 when VoIP is configured. Remote attackers can cause device or process reload by sending unspecified valid SIP messages.
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
= 4.1= 4.2= 4.3
Unified Communications ManagerApplication
= 4.1= 5.0= 5.1= 6.1
iOSOperating system
= 12.2= 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' on the device CLI and note the firmware version in the output (look for 12.2, 12.3, or 12.4 in the version string)Affected if The displayed iOS version begins with 12.2, 12.3, or 12.4
-
Identify Cisco Unified Communications Manager versionAccess the Cisco Unified Communications Manager Administration interface, go to 'Help > About' or run 'admin:show version' from the CLI, and note the version numberAffected if The installed version is 4.1, 4.2, 4.3, 5.0, 5.1, or 6.1
-
Verify SIP protocol is configuredRun 'show running-config | include sip' or 'show voip sip' in the iOS CLI to check if SIP is enabled; for Unified Communications Manager, check under 'System > Cisco SIP' in the administration interfaceAffected if SIP protocol configuration appears in the running config or is enabled in the UC Manager interface
-
Check SIP listener exposure to untrusted networksReview access control lists (ACLs) and interface configurations to determine if SIP port 5060/UDP is reachable from untrusted or external networks; use 'show ip interface' and 'show access-lists'Affected if SIP traffic on port 5060 is permitted from untrusted networks without filtering
A system is affected if it runs Cisco iOS 12.2-12.4 or Unified Communications Manager 4.1-6.1, has SIP/VoIP enabled, and exposes the SIP service to network segments that could contain malicious remote attackers.
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 to patched Cisco IOS and Unified Communications Manager versions. If immediate patching is not feasible, consider network segmentation to limit exposure to untrusted SIP traffic.
Fix this in Unified Callmanager
Scoped from the published advisory
- Consultation8.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-3801 — 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-2008-3801 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