RoomosApplication · Cisco
CVE-2019-15289
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 · uneditedMultiple vulnerabilities in the video service of Cisco TelePresence Collaboration Endpoint (CE) and Cisco RoomOS Software could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition on an affected device. The vulnerabilities are due to insufficient input validation. An attacker could exploit these vulnerabilities by sending crafted traffic to the video service of an affected endpoint. A successful exploit could allow the attacker to cause the video service to crash, resulting in a DoS condition on an affected device.
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 confidenceMultiple input validation vulnerabilities in the video service of Cisco TelePresence Collaboration Endpoint (CE) and RoomOS Software allow unauthenticated remote attackers to crash the video service by sending specially crafted traffic, resulting in denial of service.
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
all versions
Telepresence Collaboration EndpointApplication
< 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
-
Identify the installed product and software versionAccess the admin interface or use the command 'xstatus systemunit' or check the version through the web UI under 'Home > System Information'Affected if The device is running Cisco RoomOS (all versions) or Cisco TelePresence Collaboration Endpoint version below 9.8.0
-
Verify the video service is enabledCheck through the admin interface under 'Configuration > Video > Input/Output' or use command 'xCommand Video Input List' to confirm video services are configuredAffected if Video service is active and the device is in the affected version range
-
Check network exposure of the video serviceReview firewall rules or access lists that allow external traffic to reach the video service ports (typically 5060/5061 for SIP, or RTSP ports)Affected if The video service is accessible from untrusted networks and the device version is affected
-
Look for service crash indicatorsMonitor logs via 'xCommand SystemLogs Diagnostic' or check the web UI status page for unexpected video service restarts or downtimeAffected if Video service crashes occur without corresponding updates or known issues, and version is within affected range
The environment is affected if the device runs Cisco RoomOS (any version) or Cisco TelePresence Collaboration Endpoint software version below 9.8.0 and has its video service exposed to network traffic.
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 Cisco's security updates for the affected CE and RoomOS software versions. Restrict network access to the video service to trusted sources as a compensating control until patches can be applied.
Fix this in Roomos
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15289 — 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-15289 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