dbcve.org
Telepresence Tx9000 FirmwareOperating system · Cisco

CVE-2018-0326

MEDIUM · 6.1 CVSS v3.0 Published 2018-05-17
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 UI of Cisco TelePresence Server Software could allow an unauthenticated, remote attacker to conduct a cross-frame scripting (XFS) attack against a user of the web UI of the affected software. The vulnerability is due to insufficient protections for HTML inline frames (iframes) by the web UI of the affected software. An attacker could exploit this vulnerability by persuading a user of the affected UI to navigate to an attacker-controlled web page that contains a malicious HTML iframe. A successful exploit could allow the attacker to conduct click-jacking or other client-side browser attacks on the affected system. Cisco Bug IDs: CSCun79565.

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

This is a cross-frame scripting (XFS) vulnerability in the Cisco TelePresence Server web UI. The application fails to properly restrict how HTML inline frames (iframes) can be embedded, allowing attackers to trick users into interacting with the legitimate UI through a malicious transparent iframe overlay. This enables click-jacking attacks where user clicks are hijacked to perform unintended actions.

MitigationConfigure the web server to send X-Frame-Options: DENY or X-Frame-Options: SAMEORIGIN, or implement Content-Security-Policy with frame-ancestors directive to prevent the UI from being embedded in iframes on untrusted domains.

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
Telepresence Tx9000 FirmwareOperating system
Affected:= 10.0\(2.98000.99\)

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. Identify the Cisco TelePresence device model
    Access the device web UI or check the device hardware label to confirm it is a Cisco TelePresence Tx9000 model.
    Affected if The device is a Cisco TelePresence Tx9000
  2. Check the firmware version
    Log into the device admin interface and navigate to System Information or Diagnostics to view the installed firmware version. Compare against 10.0(2.98000.99).
    Affected if The firmware version is exactly 10.0(2.98000.99)
  3. Determine if the web UI is enabled and accessible
    Attempt to access the web interface over HTTP/HTTPS on the device management IP address. Confirm the TelePresence Server web UI loads in a browser.
    Affected if The web UI is accessible and responds to requests
  4. Inspect HTTP response headers for frame-embedding protection
    Use a browser developer tool or curl command to capture HTTP headers from a request to the web UI (e.g., curl -I https://<device-ip>). Look for X-Frame-Options header (DENY or SAMEORIGIN) or Content-Security-Policy header containing frame-ancestors directive.
    Affected if Neither X-Frame-Options nor CSP with frame-ancestors is present in the HTTP response headers

A user is affected if they are running the specific firmware version 10.0(2.98000.99) on a Cisco TelePresence Tx9000 with the web UI exposed and missing X-Frame-Options or CSP frame-ancestors protection in responses.

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

Configure the web server to send X-Frame-Options: DENY or X-Frame-Options: SAMEORIGIN, or implement Content-Security-Policy with frame-ancestors directive to prevent the UI from being embedded in iframes on untrusted domains.

Fix this in Telepresence Tx9000 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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