Unified Communications ManagerApplication · Cisco
CVE-2019-15272
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 web-based interface of Cisco Unified Communications Manager and Cisco Unified Communications Manager Session Management Edition (SME) could allow an unauthenticated, remote attacker to bypass security restrictions. The vulnerability is due to improper handling of malformed HTTP methods. An attacker could exploit this vulnerability by sending a crafted HTTP request to the affected system. A successful exploit could allow the attacker to gain unauthorized access to the system.
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 confidenceA vulnerability in the web-based interface of Cisco Unified Communications Manager and Cisco Unified Communications Manager Session Management Edition allows unauthenticated remote attackers to bypass security restrictions by sending malformed HTTP requests with improperly handled HTTP methods.
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
= 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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Cisco UCM product installationLog into the Cisco Unified Communications Manager admin interface and navigate to About > Version, or run 'show version' via the CLI to identify the product (Cisco Unified Communications Manager or Cisco Unified Communications Manager Session Management Edition).Affected if The system is running Cisco Unified Communications Manager or Cisco Unified Communications Manager Session Management Edition.
-
Check installed version against affected buildsLocate the exact version string shown in About > Version or 'show version' output. Compare it to these affected versions: 10.5(2.10000.5), 11.5(1.10000.6), 12.0(1.10000.10), or 12.5(1.10000.22).Affected if The installed version matches exactly one of these four specific builds.
-
Verify web interface is enabledConfirm the Cisco UCM web-based management interface is accessible by attempting to reach the admin portal (typically port 8443 or 443) or checking via CLI: 'show webapp status' or 'utils service list' to verify the Cisco Tomcat service is running.Affected if The web interface service is active and reachable.
-
Check network exposure of management interfaceReview firewall rules, ACLs, or network segmentation to determine if the web management interface is exposed to untrusted networks. Use 'show run | include http' or review access lists via CLI.Affected if The web interface is accessible from networks outside the trusted internal environment.
You are affected if your system is Cisco Unified Communications Manager or Cisco Unified Communications Manager Session Management Edition running exactly version 10.5(2.10000.5), 11.5(1.10000.6), 12.0(1.10000.10), or 12.5(1.10000.22) AND the web-based management interface is enabled and accessible.
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 dataApply the vendor patch from Cisco for CVE-2019-15272. Until the patch is applied, restrict exposure of the web interface to untrusted networks and monitor for anomalous HTTP traffic.
Fix this in Unified Communications Manager
Scoped from the published advisory
- Consultation4.0 h
- Implementation4.0 h
- Testing6.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 $4,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15272 — 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-15272 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