Telepresence Codec C40 FirmwareOperating system · Cisco
CVE-2019-12622
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 · uneditedA vulnerability in Cisco RoomOS Software could allow an authenticated, local attacker to write files to the underlying filesystem with root privileges. The vulnerability is due to insufficient permission restrictions on a specific process. An attacker could exploit this vulnerability by logging in to an affected device with remote support credentials and initiating the specific process on the device and sending crafted data to that process. A successful exploit could allow the attacker to write files to the underlying file system with root privileges.
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 · moderate confidenceA local privilege escalation vulnerability in Cisco RoomOS Software allows an authenticated attacker with remote support credentials to write arbitrary files to the filesystem with root privileges due to insufficient permission restrictions on a specific process.
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 Codec C40 FirmwareOperating system
all versions
Telepresence Codec C60 FirmwareOperating system
all versions
Telepresence Codec C90 FirmwareOperating system
all versions
RoomosOperating system
<= 9.7.2> 9.7.3, < 9.8.0CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Check the installed RoomOS firmware versionAccess the device web interface and navigate to Settings > System Information, or use CLI command 'xstatus systemunit' to retrieve the firmware versionAffected if The version is Cisco RoomOS <= 9.7.2, or > 9.7.3 and < 9.8.0, or if the device is a Telepresence Codec C40, C60, or C90 running any firmware version
-
Verify if remote support access is enabledCheck the device configuration via web interface at Setup > Administration > Remote Support, or use CLI command 'xconfiguration systemunit remoteaccess: mode' to see if remote support is enabledAffected if Remote support access is currently enabled on the device
-
Confirm remote support credentials existList configured remote support users via CLI command 'xcommand userlist' or check for the presence of remote support accounts in the system configurationAffected if Remote support user accounts are configured or exist on the system
-
Identify processes running with elevated privilegesUse CLI command 'ps' or examine the process list to identify processes associated with remote support functionality that may have root-level file write capabilitiesAffected if A specific support or maintenance process is running with root privileges and allows file operations
A user is affected if the device runs a vulnerable RoomOS version or is an affected Telepresence Codec model AND remote support is enabled with credentials configured, allowing an authenticated attacker to escalate privileges via the vulnerable process.
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 data9.8.0
Apply the Cisco software update for RoomOS that addresses this vulnerability. Until patched, strictly limit and monitor access to remote support credentials and restrict local access to trusted personnel only.
Fix this in Telepresence Codec C40 Firmware
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-12622 — 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-2019-12622 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