Unified Communications ManagerApplication · Cisco
CVE-2008-1745
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 · uneditedCisco Unified Communications Manager (CUCM) 5.x before 5.1(2) and 6.x before 6.1(1) allows remote attackers to cause a denial of service (service interruption) via a SIP JOIN message with a malformed header, aka Bug ID CSCsi48115.
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 confidenceCisco Unified Communications Manager versions 5.x before 5.1(2) and 6.x before 6.1(1) contain a vulnerability in SIP protocol handling where a malformed SIP JOIN message header causes the service to crash, resulting in denial of service. The vulnerability is remotely exploitable by network-adjacent attackers without authentication.
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 Communications ManagerApplication
= 4.1= 4.2= 4.3= 5.1= 6.0= 6.1CVSS 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
- Complete
AV:N/AC:L/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.
-
Determine CUCM versionLog into the CUCM server via CLI (SSH) and run 'show version' or access the Cisco Unified Administration interface to view the version informationAffected if The installed version is 4.1, 4.2, 4.3, 5.1, 6.0, or 6.1 (any of the listed affected versions)
-
Verify SIP service is enabledCheck CUCM service activation status via the Cisco Unified Serviceability page or CLI command 'show service' to confirm if the SIP service is runningAffected if The SIP service (SIP Proxy or SIP Station) is enabled and the version is one of the affected releases listed above
-
Check SIP network exposureReview firewall rules and network ACLs to determine if UDP/TCP port 5060 (SIP) is open to network access beyond trusted internal segmentsAffected if SIP ports are accessible from network-adjacent (untrusted) segments rather than being restricted to trusted management networks only
If the installed CUCM version is 4.1, 4.2, 4.3, 5.1, 6.0, or 6.1 AND the SIP service is enabled and network-accessible, the environment is vulnerable to this CVE.
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 dataApply the vendor-provided patches by upgrading CUCM to version 5.1(2) or later for 5.x releases, or 6.1(1) or later for 6.x releases. If immediate patching is not possible, consider SIP traffic filtering at network borders to reduce attack surface.
Fix this in Unified Communications Manager
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-1745 — 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-1745 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