dbcve.org
Unified Communications ManagerApplication · Cisco

CVE-2019-1837

HIGH · 7.5 CVSS v3.0 Published 2019-04-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 User Data Services (UDS) API of Cisco Unified Communications Manager (Unified CM) could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition on the management GUI. The vulnerability is due to improper validation of input parameters in the UDS API requests. An attacker could exploit this vulnerability by sending a crafted request to the UDS API of an affected device. A successful exploit could allow the attacker to make the A Cisco DB service quit unexpectedly, preventing admin access to the Unified CM management GUI. Manual intervention may be required to restore normal operation. Software versions 10.5, 11.5, 12.0, 12.5 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

A vulnerability in the User Data Services (UDS) API of Cisco Unified Communications Manager allows unauthenticated remote attackers to send crafted requests with improperly validated input parameters. This causes the Cisco DB service to crash unexpectedly, preventing admin access to the Unified CM management GUI and requiring manual intervention to restore normal operation.

MitigationApply the Cisco software update for Unified CM versions 10.5, 11.5, 12.0, and 12.5 as provided by Cisco to address the improper input validation in the UDS API.

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
Unified Communications ManagerApplication
Affected:= 10.5\(2.10000.5\)= 11.5\(1.10000.6\)= 12.0\(1.10000.10\)= 12.5\(1.10000.22\)

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/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 checks

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

  1. Check Cisco UCM version via CLI
    Log into the Cisco Unified Communications Manager server via SSH and run the command: 'show version' or 'utils system version'. Look for the exact version string in the format like 10.5(2)10000.5, 11.5(1)10000.6, 12.0(1)10000.10, or 12.5(1)10000.22.
    Affected if The displayed version matches exactly 10.5(2)10000.5, 11.5(1)10000.6, 12.0(1)10000.10, or 12.5(1)10000.22.
  2. Check Cisco UCM version via web GUI
    Access the Unified CM Administration web interface and navigate to Help > About. Record the exact version number displayed.
    Affected if The version shown matches any of the four affected versions listed in the CVE.
  3. Verify UDS API accessibility
    Confirm the Cisco UCM management GUI is accessible by attempting to reach the web interface on the configured IP/hostname. The vulnerability is triggered via the UDS API endpoint which is typically exposed on the same management interface.
    Affected if The management GUI is accessible and the server is running one of the affected versions.
  4. Check for service disruption symptoms
    Attempt to access the Cisco UCM Administration web interface. Also check if the Cisco DB service is running via CLI command: 'show process list | grep DB' or by logging into the operating system and checking service status.
    Affected if The web interface is unresponsive or the Cisco DB service shows as stopped on an affected version.

If your installed Cisco Unified Communications Manager version exactly matches 10.5(2)10000.5, 11.5(1)10000.6, 12.0(1)10000.10, or 12.5(1)10000.22 and the management interface is accessible, your environment is affected by this CVE.

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 Cisco software update for Unified CM versions 10.5, 11.5, 12.0, and 12.5 as provided by Cisco to address the improper input validation in the UDS API.

Fix this in Unified Communications Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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