dbcve.org
Unified Communications ManagerApplication · Cisco

CVE-2013-3397

MEDIUM · 6.8 CVSS v2.0 Published 2013-06-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/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
Cross-site request forgery (CSRF) vulnerability in the Unified Serviceability component in Cisco Unified Communications Manager (CUCM) allows remote attackers to hijack the authentication of arbitrary users for requests that perform Unified Serviceability actions, aka Bug ID CSCuh10298.

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 confidence

A cross-site request forgery (CSRF) vulnerability exists in the Unified Serviceability component of Cisco Unified Communications Manager (CUCM). Attackers can exploit this by tricking authenticated users into visiting malicious web pages, causing the user's browser to send unintended requests to the CUCM Unified Serviceability interface, allowing unauthorized actions to be performed with the hijacked authentication.

MitigationImplement anti-CSRF tokens for all form submissions and request validation within the Unified Serviceability component, and configure SameSite cookie attributes to prevent cross-origin request forgery.

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
Affected:all versions

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
M
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:M/Au:N/C:P/I:P/A:P

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 Communications Manager is running
    Check for CUCM processes or services on the system. On the server console, run: 'utils service list' or check for processes like 'Cisco Tomcat' or 'Cisco CCM Service'. Network scan for typical CUCM ports (8443, 443, 8080).
    Affected if CUCM is installed and running on the system.
  2. Locate the Unified Serviceability web interface
    Access the Unified Serviceability interface via browser or curl. Typical paths include: https://< cucm_host >/ccmservice/ or https://< cucm_host >:8443/ccmservice/. Check if the login page loads.
    Affected if The Unified Serviceability web interface is accessible.
  3. Verify session handling accepts cookies
    Attempt to authenticate to the Unified Serviceability interface and observe if session cookies are set. Use browser dev tools or curl to check for Set-Cookie headers upon login.
    Affected if The interface establishes authenticated sessions with cookies without SameSite attributes.
  4. Check for CSRF token implementation
    Submit a test form request to the Unified Serviceability interface and inspect whether a CSRF token or anti-CSRF mechanism is required. Compare requests with and without a token parameter.
    Affected if Form submissions do not require valid anti-CSRF tokens.
  5. Confirm network accessibility
    Determine if the Unified Serviceability interface is exposed to untrusted networks. Check firewall rules, ACLs, or reverse proxy configurations that allow access to the CUCM web interfaces.
    Affected if The interface is reachable from networks beyond the trusted administrative zone.

The environment is affected if Cisco Unified Communications Manager is running with its Unified Serviceability web interface accessible and accepting authenticated sessions without proper CSRF protection mechanisms.

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

Implement anti-CSRF tokens for all form submissions and request validation within the Unified Serviceability component, and configure SameSite cookie attributes to prevent cross-origin request forgery.

Fix this in Unified Communications Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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