dbcve.org
Unified Communications ManagerApplication · Cisco

CVE-2013-3472

MEDIUM · 6.8 CVSS v2.0 Published 2013-08-29
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 Enterprise License Manager (ELM) in Cisco Unified Communications Manager (CM) allows remote attackers to hijack the authentication of arbitrary users for requests that make ELM modifications, aka Bug ID CSCui58210.

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

Cross-site request forgery (CSRF) vulnerability in Cisco Unified Communications Manager's Enterprise License Manager (ELM) allows remote attackers to hijack authenticated user sessions and make unauthorized ELM modifications. The attack exploits the lack of anti-CSRF tokens or referer validation in the ELM web interface, enabling malicious requests to be forged on behalf of legitimate authenticated users.

MitigationApply the Cisco patch for Bug ID CSCui58210 to the Unified Communications Manager. Additionally, enable CSRF protections in the web application and consider network segmentation to limit exposure of the management interface to trusted networks.

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 installed
    Check system for CUCM components or consult inventory systems for Cisco UC installations. Common indicators: look for Cisco Tomcat service, CUCM-specific processes, or check network for CUCM management ports (commonly 8443, 8080 for web interfaces).
    Affected if CUCM is installed and running in the environment
  2. Determine if Enterprise License Manager web interface is exposed
    Attempt to access the ELM interface by navigating to the CUCM hostname/IP with path '/elm/' or '/ccmadmin/elm' over HTTPS. Check if the login page loads. Common ports are 8443 or 443 on the CUCM server.
    Affected if The ELM web interface is accessible and responds to requests
  3. Verify CUCM version against patch status
    Access the CUCM Administration interface (typically at /ccmadmin), look for the 'About' page or version information in the system dashboard. Compare the version number to known patched releases for CSCui58210.
    Affected if Running a version prior to the patch release date (2013) or unable to confirm patch application
  4. Assess network exposure of management interface
    Review firewall rules and network access controls to determine if the CUCM/ELM web interface is accessible from untrusted networks. Check if the management interface is exposed to the internet or unnecessary internal networks.
    Affected if The ELM management interface is accessible from untrusted networks or the internet without VPN/segmentation

You are affected if Cisco Unified Communications Manager is installed with the ELM web interface accessible and the system has not had the CSCui58210 patch applied or is running an older pre-patch version.

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

Apply the Cisco patch for Bug ID CSCui58210 to the Unified Communications Manager. Additionally, enable CSRF protections in the web application and consider network segmentation to limit exposure of the management interface to trusted networks.

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-3472 — 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-3472 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