dbcve.org
Telepresence Video Communication ServerApplication · Cisco

CVE-2019-1679

MEDIUM · 5.0 CVSS v3.1 Published 2019-02-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
56/100
Remediation priority · Elevated
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 web interface of Cisco TelePresence Conductor, Cisco Expressway Series, and Cisco TelePresence Video Communication Server (VCS) Software could allow an authenticated, remote attacker to trigger an HTTP request from an affected server to an arbitrary host. This type of attack is commonly referred to as server-side request forgery (SSRF). The vulnerability is due to insufficient access controls for the REST API of Cisco Expressway Series and Cisco TelePresence VCS. An attacker could exploit this vulnerability by submitting a crafted HTTP request to the affected server. Versions prior to XC4.3.4 are affected.

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

This is a Server-Side Request Forgery (SSRF) vulnerability in the REST API of Cisco TelePresence VCS and Expressway Series. An authenticated remote attacker can submit crafted HTTP requests to cause the affected server to initiate connections to arbitrary hosts, potentially enabling port scanning, internal service enumeration, or firewall bypass.

MitigationUpgrade to Cisco VCS/Expressway version XC4.3.4 or later to remediate this vulnerability.

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 Video Communication ServerApplication
Affected:< x12.5
Telepresence ConductorApplication
Affected:< xc4.3.4

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
Low
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/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 the installed Cisco TelePresence product
    Access the admin interface or check system documentation to determine whether the system is running Cisco TelePresence Video Communication Server (VCS) or Cisco TelePresence Conductor.
    Affected if The product is either Cisco VCS or Cisco Conductor.
  2. Determine the installed version number
    Log into the admin web interface and navigate to the version or system information page, or use the CLI command 'version' to retrieve the exact software version.
    Affected if Version cannot be determined or is lower than x12.5 for VCS or lower than xc4.3.4 for Conductor.
  3. Confirm the product and version against the affected ranges
    Compare the identified version to the vulnerable ranges: VCS versions below x12.5 and Conductor versions below xc4.3.4 are affected.
    Affected if The installed version falls below x12.5 for VCS or below xc4.3.4 for Conductor.
  4. Verify REST API accessibility
    Check if the REST API endpoint is accessible externally or from untrusted networks by reviewing firewall rules and interface bindings in the admin configuration.
    Affected if The REST API is exposed to untrusted networks without proper network segmentation.
  5. Review REST API authentication configuration
    In the admin interface, navigate to the API or authentication settings to confirm whether authentication is required and properly configured for REST API access.
    Affected if REST API authentication is disabled or uses default credentials, increasing exploitability.

The environment is affected if the installed product is Cisco VCS below version x12.5 or Cisco Conductor below version xc4.3.4, with the REST API accessible and potentially lacking proper authentication controls.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Cisco VCS/Expressway version XC4.3.4 or later to remediate this vulnerability.

Fix this in Telepresence Video Communication Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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