Unified Communications ManagerApplication · Cisco
CVE-2013-3450
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 · uneditedCross-site request forgery (CSRF) vulnerability in the User WebDialer page in Cisco Unified Communications Manager (Unified CM) allows remote attackers to hijack the authentication of arbitrary users for requests that dial calls, aka Bug ID CSCui13028.
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 confidenceCSRF vulnerability in Cisco Unified Communications Manager's User WebDialer allows remote attackers to trick authenticated users into unknowingly initiating phone calls. The attacker crafts malicious requests that the victim's browser sends while authenticated, exploiting the lack of proper CSRF token validation on the WebDialer endpoint.
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
all versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify WebDialer service statusLog into Cisco Unified Communications Manager Administration, go to System > Service Parameters, select the server and verify if the WebDialer service (Cisco Web Dialer) is enabled and running.Affected if WebDialer service is enabled and running on the CUCM server
-
Check WebDialer configuration for CSRF token validationAccess the WebDialer configuration files (typically in /usr/local/platform/conf or via the Cisco Unified OS Administration interface) and examine the webdialer.properties or related configuration for the presence of CSRF token validation settings.Affected if CSRF token (synchronizer token) validation is not configured or is disabled in WebDialer settings
-
Inspect request origin and referer header validationExamine the WebDialer servlet or application configuration for validateOrigin or validateReferer settings. These should be enabled to prevent CSRF attacks.Affected if Origin/referer header validation is not enabled in the WebDialer endpoint configuration
-
Review WebDialer endpoint authentication mechanismCheck the WebDialer makeCall.jsp or equivalent servlet to determine if requests to the makeCall endpoint include and validate anti-CSRF tokens on each request.Affected if The WebDialer makeCall endpoint does not require valid CSRF tokens for incoming requests
A user is affected if WebDialer is enabled and the CSRF protection mechanisms (synchronizer tokens and origin/referer validation) are not properly configured or enabled.
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 dataEnable anti-CSRF protections (synchronizer tokens) on the WebDialer functionality and validate request origin/referer headers; apply Cisco's official patch for Unified CM when available.
Fix this in Unified Communications Manager
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-3450 — 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-2013-3450 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