Telepresence Collaboration EndpointApplication · Cisco
CVE-2019-15274
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 the CLI of Cisco TelePresence Collaboration Endpoint (CE) Software could allow an authenticated, local attacker to perform command injections. The vulnerability is due to insufficient input validation. An attacker could exploit this vulnerability by authenticating as an administrative level user within the restricted shell and submitting malicious input to a specific command. A successful exploit could allow the attacker to execute previously staged code from the underlying filesystem.
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 command injection vulnerability exists in the CLI of Cisco TelePresence Collaboration Endpoint (CE) Software due to insufficient input validation. An attacker who has authenticated as an administrative-level user within the restricted shell can submit malicious input to specific commands, allowing execution of pre-staged code from the filesystem.
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 Collaboration EndpointApplication
< 9.8.1CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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 checksWork through these to decide whether this CVE applies to you.
-
Determine the installed Cisco TelePresence CE Software versionLog into the CLI and run the command to display system version information (commonly 'show version' or similar version display command in the TelePresence CLI)Affected if The displayed version number is less than 9.8.1 (for example, 9.7.x, 9.6.x, or earlier)
-
Confirm administrative user access existsCheck if any user accounts with administrative or root-level privileges are configured in the system (review user accounts via CLI command like 'show account' or through the administration interface)Affected if Administrative or elevated-privilege user accounts exist in the system
-
Verify CLI access is availableConfirm that the restricted shell CLI interface is accessible (test login to the CLI with an administrative account)Affected if Authenticated CLI access to the restricted shell is possible with administrative credentials
-
Check for unusual pre-staged filesInspect the filesystem for unexpected or unauthorized files that could be targeted for execution via the command injection (examine common staging locations if you have filesystem access)Affected if Suspicious files exist on the system that were not placed by authorized administrators
The environment is affected if the installed Cisco TelePresence CE Software version is below 9.8.1 AND administrative CLI access is available, allowing an authenticated attacker to inject commands through specific CLI inputs.
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.1
Apply the Cisco security patch for CVE-2019-15274. Until patched, limit administrative access to trusted personnel only and monitor CLI activity for unusual commands.
Fix this in Telepresence Collaboration Endpoint
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15274 — 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-15274 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