dbcve.org
Cloud Access ConnectorApplication · Teradici

CVE-2020-13176

MEDIUM · 6.1 CVSS v3.1 Published 2020-08-11
Fix available
A fix is available. Upgrade to 2020-04-24 or later.
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
The Management Interface of the Teradici Cloud Access Connector and Cloud Access Connector Legacy for releases prior to April 24, 2020 (v16 and earlier for the Cloud Access Connector) contains a stored cross-site scripting (XSS) vulnerability which allows a remote unauthenticated attacker to poison log files with malicious JavaScript via the login page which is executed when an administrator views the logs within the application.

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

A stored cross-site scripting (XSS) vulnerability in the Management Interface of Teradici Cloud Access Connector (v16 and earlier) and Cloud Access Connector Legacy allows remote unauthenticated attackers to inject malicious JavaScript into log files via the login page. This injected script executes when an administrator later views the logs within the application.

MitigationUpgrade to Cloud Access Connector v16.1 or later (released after April 24, 2020), and ensure proper input validation and output encoding are implemented on both the login page and log viewing interface.

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
Cloud Access ConnectorApplication
Affected:<= 16
Cloud Access Connector LegacyApplication
Affected:< 2020-04-24

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.1/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 installed Cloud Access Connector version
    Access the management interface or check system packages/diagnostics to find the installed version number. For CLI, run: 'dmcli --version' or check installed RPM/DEB package version.
    Affected if Version is 16 or earlier for Cloud Access Connector, or the software is identified as 'Legacy' with a version/build date before 2020-04-24
  2. Confirm Management Interface is enabled
    Verify the Cloud Access Connector management interface is accessible and running. Check if port 8443 (default management port) is listening, or confirm the web UI is reachable.
    Affected if The management interface is exposed and accessible to network users
  3. Locate and inspect log files
    Access the system where Cloud Access Connector is installed and locate the log directory. Common paths: /var/log/teradici/ or within the application data directory. Open the log files that record login attempts.
    Affected if Log files exist and contain unsanitized user input from the login page (look for raw username strings that may contain script tags or HTML)
  4. Verify log viewing functionality
    Log into the management interface as an administrator and navigate to the log viewing section (typically under 'Diagnostics' or 'Logs'). Check if the interface renders log content without sanitization.
    Affected if The log viewer displays raw, unescaped content from login attempts, allowing injected script to execute in the browser

The environment is affected if running Cloud Access Connector version 16 or earlier (or Legacy version before 2020-04-24), the management interface is accessible, and log files can be viewed through the web UI without output encoding.

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
Upgrade available Upgrade to 2020-04-24 or later
Fixed in 2020-04-24
Interim mitigation

Upgrade to Cloud Access Connector v16.1 or later (released after April 24, 2020), and ensure proper input validation and output encoding are implemented on both the login page and log viewing interface.

Fix this in Cloud Access Connector Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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