Telepresence Video Communication Server SoftwareApplication · Cisco
CVE-2015-0772
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 TelePresence Video Communication Server (VCS) X8.5RC4 allows remote attackers to cause a denial of service (CPU consumption or device outage) via a crafted SDP parameter-negotiation request in an SDP session during a SIP connection, aka Bug ID CSCut42422.
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 confidenceA vulnerability in the Session Initiation Protocol (SIP) and Session Description Protocol (SDP) handling of Cisco TelePresence Video Communication Server X8.5RC4 allows remote attackers to send crafted SDP parameter-negotiation requests during SIP connections, causing excessive CPU consumption or complete device outage.
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
Telepresence Video Communication Server SoftwareApplication
= x8.5CVSS 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 the installed Cisco TelePresence Video Communication Server software versionAccess the administration web interface or use the CLI command 'version' to retrieve the running software versionAffected if The displayed version is exactly x8.5 or x8.5RC4
-
Verify SIP service is enabled and accessibleCheck the SIP configuration via the web interface under 'Configuration > SIP' or use CLI 'show sip' to confirm SIP proxy service is runningAffected if SIP service is enabled and the device accepts SIP connections from untrusted sources
-
Confirm network exposure of the SIP serviceReview firewall rules or access control lists protecting the VCS to determine if the SIP port (5060/5061) is exposed to untrusted networksAffected if The SIP service is reachable from external or untrusted network segments without filtering or rate limiting
A user is affected if the Cisco TelePresence Video Communication Server is running version x8.5 and has SIP service exposed to untrusted networks, allowing remote attackers to send crafted SDP parameter-negotiation requests that cause CPU exhaustion or device outage.
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 patch from Cisco for this vulnerability (Bug ID CSCut42422); as a compensating control, consider implementing SIP traffic filtering or rate limiting at network boundaries to block malicious SIP/SDP requests.
Fix this in Telepresence Video Communication Server Software
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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 $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0772 — 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-2015-0772 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