Unified Communications ManagerApplication · Cisco
CVE-2019-12711
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 access sensitive information or cause a denial of service (DoS) condition. The vulnerability is due to improper restrictions on XML entities. An attacker could exploit this vulnerability by sending malicious requests to an affected system that contain references in XML entities. A successful exploit could allow the attacker to retrieve files from the local system, resulting in the disclosure of sensitive information, or cause the application to consume available resources, resulting in a 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 confidenceThis is an XML External Entity (XXE) injection vulnerability in the web-based management interface of Cisco Unified Communications Manager and Cisco Unified Communications Manager Session Management Edition. An unauthenticated remote attacker can exploit improper restrictions on XML entities to retrieve sensitive files from the local system or cause denial of service by exhausting server resources.
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
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L
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 if Cisco Unified Communications Manager or SME is installedCheck the system for Cisco Unified Communications Manager or Session Management Edition by reviewing installed software packages or running 'show version' on the Cisco device CLI if applicable.Affected if The product is Cisco Unified Communications Manager or Cisco Unified Communications Manager Session Management Edition.
-
Determine the installed CUCM or SME versionUse the Cisco CLI command 'show version' or access the Disaster Recovery System (DRS) backup screen to view the current software version. Compare the version number against the affected releases: 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 exactly matches one of the listed affected version strings.
-
Verify the web-based management interface is accessibleConfirm that the Cisco Unified Communications Manager web interface (typically on port 8443 or 443) is reachable from the network. Attempt to access the login page via HTTPS.Affected if The web management interface is exposed and reachable on the network.
-
Check if XML functionality is enabled in the web interfaceReview the web interface configuration to determine if XML parsing capabilities are active. This may be observable through normal web interface operation or by reviewing the server configuration for XML parser settings.Affected if XML processing is enabled and the web interface is operational.
The system is affected if it runs Cisco Unified Communications Manager or SME version 10.5(2.10000.5), 11.5(1.10000.6), 12.0(1.10000.10), or 12.5(1.10000.22) with the web-based management interface accessible and XML parsing enabled.
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 Cisco security patches for CVE-2019-12711 and disable external entity processing in XML parsers used by the web interface. Restrict web interface access to authorized personnel while patches are applied.
Fix this in Unified Communications Manager
Scoped from the published advisory
- Consultation6.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,296.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-12711 — 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-12711 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