dbcve.org
Unified PresenceApplication · Cisco

CVE-2012-3935

HIGH · 7.8 CVSS v2.0 Published 2012-09-12
Fix available
A fix is available. Upgrade to after 8.6 or later.
See remediation →
87/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
Cisco Unified Presence (CUP) before 8.6(3) and Jabber Extensible Communications Platform (aka Jabber XCP) before 5.3 allow remote attackers to cause a denial of service (process crash) via a crafted XMPP stream header, aka Bug ID CSCtu32832.

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

The vulnerability is a denial of service flaw in Cisco Unified Presence and Jabber XCP's XMPP (Extensible Messaging and Presence Protocol) stream header parsing. Attackers can send a crafted XMPP stream header to crash the affected process, causing service disruption. The issue stems from improper handling of malformed XMPP protocol elements during initial stream establishment.

MitigationUpgrade Cisco Unified Presence to version 8.6(3) or later, and Jabber XCP to version 5.3 or later. If immediate patching is not feasible, restrict network access to XMPP ports (default 5222/5223) from untrusted sources using firewalls or ACLs 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 PresenceApplication
Affected:<= 8.6\(2\)= 1.0= 6.0= 6.0\(1\)= 6.0\(2\)= 6.0\(3\)= 6.0\(4\)= 6.0\(5\)= 6.0\(6\)= 6.0\(7\)= 6.0_1= 6.0_2
Jabber Extensible Communications PlatformApplication
Affected:<= 5.2

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Cisco Unified Presence or Jabber XCP is installed
    Check for running processes or installed services named 'Cisco Unified Presence', 'cup', 'Jabber', or 'XCP' using commands like 'ps aux | grep -iE "(cup|jabber|xcp)"' or review installed software via system package manager
    Affected if Either Cisco Unified Presence or Jabber XCP software is present on the system
  2. Check the installed version of Cisco Unified Presence
    Access the Cisco Unified Presence server CLI and run 'show version' or access the admin web interface and look for the version displayed on the dashboard or in 'System > Server > Version'
    Affected if The version is 8.6(2) or lower, or matches any of these specific versions: 1.0, 6.0, 6.0(1), 6.0(2), 6.0(3), 6.0(4), 6.0(5), 6.0(6), 6.0(7), 6.0_1, or 6.0_2
  3. Check the installed version of Jabber XCP
    Access the Jabber XCP admin interface or check the installed package version using system commands or configuration files in the installation directory
    Affected if The version is 5.2 or lower
  4. Verify XMPP service is enabled and running
    Check if the XMPP service is active by reviewing running services or checking if ports 5222 (client) or 5223 (SSL) are listening using 'netstat -an | grep -E "(5222|5223)"' or 'ss -tlnp | grep -E "(5222|5223)"'
    Affected if XMPP ports 5222 or 5223 are in LISTEN state, indicating the vulnerable service is exposed

You are affected if Cisco Unified Presence version 8.6(2) or lower (or any of the specific versions listed) or Jabber XCP version 5.2 or lower is installed AND the XMPP service is running and accessible.

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
Upgrade available Upgrade to a release after 8.6
Interim mitigation

Upgrade Cisco Unified Presence to version 8.6(3) or later, and Jabber XCP to version 5.3 or later. If immediate patching is not feasible, restrict network access to XMPP ports (default 5222/5223) from untrusted sources using firewalls or ACLs to reduce attack surface.

Fix this in Unified Presence Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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