dbcve.org
RoomosApplication · Cisco

CVE-2020-3336

HIGH · 7.2 CVSS v3.1 Published 2020-06-18
Fix available
A fix is available. Upgrade to 9.9.4 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
A vulnerability in the software upgrade process of Cisco TelePresence Collaboration Endpoint Software and Cisco RoomOS Software could allow an authenticated, remote attacker to modify the filesystem to cause a denial of service (DoS) or gain privileged access to the root filesystem. The vulnerability is due to insufficient input validation. An attacker with administrative privileges could exploit this vulnerability by sending requests with malformed parameters to the system using the console, Secure Shell (SSH), or web API. A successful exploit could allow the attacker to modify the device configuration or cause a DoS.

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 vulnerability in the software upgrade process of Cisco TelePresence Collaboration Endpoint Software and Cisco RoomOS Software allows an authenticated attacker with administrative privileges to send malformed parameters via console, SSH, or web API. This insufficient input validation enables modification of the filesystem, potentially granting root access or causing denial of service.

MitigationApply the vendor patch from Cisco when available. Prior to patching, restrict administrative access to trusted personnel only and monitor for suspicious upgrade-related API requests or console activity.

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
RoomosApplication
Affected:all versions
Telepresence Collaboration EndpointApplication
Affected:< 9.9.4>= 9.10.0, <= 9.10.2>= 9.12.0, <= 9.12.3

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

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 installed software version
    Access the device via web UI, CLI (SSH/console), or API and retrieve the current firmware/software version. For CLI, use 'show version' or 'systemtools version'. For API, query the /getxml endpoint or similar status endpoint.
    Affected if The installed version falls outside the fixed releases: Cisco RoomOS (all versions are affected); Cisco TelePresence Collaboration Endpoint versions < 9.9.4, 9.10.0-9.10.2, or 9.12.0-9.12.3 are affected.
  2. Confirm administrative access is enabled
    Review user accounts with administrative or root-level privileges via the device web interface under Users or Security settings, or via CLI command 'xmlpi /config/getxml -x //User'
    Affected if Any administrative account exists and is accessible, as the attacker requires administrative privileges to exploit this vulnerability.
  3. Review upgrade process logs for anomalies
    Check system logs, upgrade logs, or audit logs for failed or malformed upgrade attempts. Access via CLI 'event logs' or web interface logs section, looking for entries around the upgrade process with unexpected parameters or errors.
    Affected if Any logs show malformed upgrade parameters, failed upgrade attempts with unexpected input, or unauthorized upgrade API requests.
  4. Audit recent filesystem changes
    Examine the device for unexpected files or modifications in system directories that could indicate filesystem manipulation. Use CLI commands like 'file list' or compare current state against known-good baseline if available.
    Affected if Unexpected files or modifications exist in system directories that were not part of a known, legitimate upgrade.

You are affected if your installed Cisco TelePresence Collaboration Endpoint version is one of the vulnerable releases (less than 9.9.4, between 9.10.0-9.10.2, or between 9.12.0-9.12.3) or if you run any version of Cisco RoomOS, and the device has administrative accounts configured.

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 9.9.4 or later
Fixed in 9.9.4
Interim mitigation

Apply the vendor patch from Cisco when available. Prior to patching, restrict administrative access to trusted personnel only and monitor for suspicious upgrade-related API requests or console activity.

Fix this in Roomos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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