Unified PresenceApplication · Cisco

CVE-2008-1158

HIGH · 7.8 CVSS v2.0 Published 2008-05-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
The Presence Engine (PE) service in Cisco Unified Presence before 6.0(1) allows remote attackers to cause a denial of service (core dump and service interruption) via malformed packets, aka Bug ID CSCsh50164.

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 Presence Engine (PE) service in Cisco Unified Presence versions before 6.0(1) is vulnerable to a remote denial of service attack. Attackers send malformed packets to the PE service, causing it to crash and generate a core dump, resulting in service interruption.

MitigationUpgrade Cisco Unified Presence to version 6.0(1) or later to obtain the patch for this vulnerability. If immediate upgrade is not feasible, consider network-level filtering to restrict untrusted sources from reaching the PE service ports.

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:= 6.0
Unified Presence ServerApplication
Affected:= 1.0= 1.0\(1\)= 1.0\(2\)= 1.0\(3\)

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 is installed
    Look for Cisco Unified Presence processes or services running on the system. On the server, check running processes for 'PE', 'Presence Engine', or 'cup' related processes using commands like 'ps -ef | grep -i presence' or review installed software listings.
    Affected if The Presence Engine (PE) service is found running on the system
  2. Determine the installed Cisco Unified Presence version
    Check the installed version of Cisco Unified Presence or Cisco Unified Presence Server. This can typically be found in system inventory, software version displays, or by querying the CUP administration interface for version information.
    Affected if The installed version is 6.0 (base version) OR versions 1.0, 1.0(1), 1.0(2), or 1.0(3) of Cisco Unified Presence Server - meaning versions before 6.0(1)
  3. Verify the Presence Engine service is network accessible
    Check if the PE service ports are exposed to the network. Identify which ports the Presence Engine listens on and verify network accessibility from untrusted sources using port scanning or firewall rules review.
    Affected if The PE service is reachable from network segments containing untrusted sources
  4. Check for recent service crashes or core dumps
    Review system logs, application logs, and core dump directories for evidence of the PE service crashing or generating core files, particularly around the time of suspicious network activity.
    Affected if The PE service has experienced unexplained crashes or generated core dumps since deployment

A system is affected if Cisco Unified Presence version 6.0 (base) or Cisco Unified Presence Server versions 1.0 through 1.0(3) is installed and the Presence Engine service is network-accessible, making it vulnerable to remote crash via malformed packets.

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

Upgrade Cisco Unified Presence to version 6.0(1) or later to obtain the patch for this vulnerability. If immediate upgrade is not feasible, consider network-level filtering to restrict untrusted sources from reaching the PE service ports.

Fix this in Unified Presence Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2008-1158 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