dbcve.org
Unified Communications ManagerApplication · Cisco

CVE-2017-12258

MEDIUM · 6.1 CVSS v3.0 Published 2017-10-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
A vulnerability in the web-based UI of Cisco Unified Communications Manager could allow an unauthenticated, remote attacker to execute a cross-frame scripting (XFS) attack. The vulnerability exists because the affected software does not provide sufficient protections for HTML inline frames (iframes). An attacker could exploit this vulnerability by directing a user of the affected software to an attacker-controlled web page that contains a malicious HTML inline frame. A successful exploit could allow the attacker to conduct click-jacking or other types of client-side browser attacks. Cisco Bug IDs: CSCve60993.

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-frame scripting (XFS) vulnerability in Cisco Unified Communications Manager web-based UI allows attackers to embed malicious iframes from attacker-controlled pages. Insufficient iframe protections enable click-jacking and other client-side browser attacks by tricking authenticated users into interacting with hidden or disguised interface elements.

MitigationAdd X-Frame-Options: DENY or SAMEORIGIN response headers and/or implement Content Security Policy with frame-ancestors directive to restrict which origins can embed the application in iframes.

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
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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. Confirm Cisco Unified Communications Manager is installed
    Check for the presence of the Cisco Unified Communications Manager application or service on the system. Look for processes named 'Cisco Unified Communications Manager' or check installed programs list.
    Affected if The product is present on the system
  2. Verify the web-based UI is accessible
    Attempt to access the Cisco Unified Communications Manager web interface via HTTP/HTTPS from the system or a test machine to confirm it responds.
    Affected if The web UI responds to requests and is network-accessible
  3. Check for X-Frame-Options response header
    Send an HTTP GET request to the web UI login page or any authenticated page and inspect the response headers for the presence of 'X-Frame-Options: DENY' or 'X-Frame-Options: SAMEORIGIN'.
    Affected if The X-Frame-Options header is missing or set to a weak value like ALLOW-FROM an untrusted origin
  4. Check for Content Security Policy frame-ancestors directive
    Inspect the HTTP response headers for 'Content-Security-Policy' and verify if the 'frame-ancestors' directive is present and restricts framing to trusted origins.
    Affected if No CSP frame-ancestors directive is defined or it allows arbitrary origins

The environment is affected if Cisco Unified Communications Manager web UI is running and lacks X-Frame-Options and CSP frame-ancestors protections, allowing untrusted sites to embed the interface in iframes.

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

Add X-Frame-Options: DENY or SAMEORIGIN response headers and/or implement Content Security Policy with frame-ancestors directive to restrict which origins can embed the application in iframes.

Fix this in Unified Communications Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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