dbcve.org
Telepresence Advanced Media GatewayApplication · Cisco

CVE-2019-15966

HIGH · 7.7 CVSS v3.1 Published 2019-11-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
83/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 web application of Cisco TelePresence Advanced Media Gateway could allow an authenticated, remote attacker to cause a denial of service (DoS) condition on an affected device. The vulnerability is due to the lack of input validation in the web application. An attacker could exploit this vulnerability by sending a crafted authenticated HTTP request to the device. An exploit could allow the attacker to stop services on an affected device. The device may become inoperable and results in a denial of service (DoS) condition.

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 exists in the web application of Cisco TelePresence Advanced Media Gateway due to insufficient input validation. An authenticated attacker can exploit this by sending crafted HTTP requests to the device, causing services to stop and resulting in a denial of service condition where the device becomes inoperable.

MitigationApply the vendor-supplied patch or firmware update from Cisco for this vulnerability. As an interim control, restrict access to the device's web management interface to trusted IP addresses only and implement network segmentation.

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 Advanced Media GatewayApplication
Affected:= 1.1

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
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm the device model
    Identify the Cisco TelePresence device by checking the system information via CLI (show version) or through the web management interface. Look for 'Advanced Media Gateway' in the product name or model description.
    Affected if The device is not a Cisco TelePresence Advanced Media Gateway (not affected)
  2. Check the installed firmware version
    Access the device CLI and run 'show version' or access the web interface and navigate to the version/system information page. Look for the exact firmware version number.
    Affected if The firmware version is exactly 1.1 (vulnerable). Versions other than 1.1 are not affected by this specific CVE.
  3. Verify the web management interface is enabled
    Check the device configuration via CLI for HTTP/HTTPS service settings, or log into the web interface to confirm it is accessible. Common commands include 'show running-config | include http' or checking the service parameters.
    Affected if The web management interface is disabled or not configured - the device may not be vulnerable as the attack requires sending HTTP requests to the web application.
  4. Assess network exposure of the web interface
    Review the device network configuration to determine if the web management interface is reachable from untrusted networks. Check interface bindings and access control lists.
    Affected if The web interface is exposed to untrusted networks (not behind firewall or ACLs) - combined with version 1.1, this increases likelihood of exploitation.

Your environment is affected if you are running Cisco TelePresence Advanced Media Gateway firmware version 1.1 with the web management interface enabled and accessible.

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

Apply the vendor-supplied patch or firmware update from Cisco for this vulnerability. As an interim control, restrict access to the device's web management interface to trusted IP addresses only and implement network segmentation.

Fix this in Telepresence Advanced Media Gateway Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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