dbcve.org
Prime License ManagerApplication · Cisco

CVE-2021-1362

HIGH · 8.8 CVSS v3.1 Published 2021-04-08
Fix available
A fix is available. Upgrade to 11.5 / 12.5 or later.
See remediation →
94/100
Remediation priority · Urgent
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 SOAP API endpoint of Cisco Unified Communications Manager, Cisco Unified Communications Manager Session Management Edition, Cisco Unified Communications Manager IM & Presence Service, Cisco Unity Connection, and Cisco Prime License Manager could allow an authenticated, remote attacker to execute arbitrary code on an affected device. This vulnerability is due to improper sanitization of user-supplied input. An attacker could exploit this vulnerability by sending a SOAP API request with crafted parameters to an affected device. A successful exploit could allow the attacker to execute arbitrary code with root privileges on the underlying Linux operating system of the affected device.

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 command injection vulnerability in the SOAP API endpoint of Cisco Unified Communications products allows authenticated remote attackers to execute arbitrary code with root privileges due to improper sanitization of user-supplied input in SOAP API requests.

MitigationApply Cisco's official security patches for CVE-2021-1362 to all affected products. Until patched, restrict network access to SOAP API endpoints and monitor for suspicious SOAP requests with unusual parameters.

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
Prime License ManagerApplication
Affected:>= 10.5\(2\), < 11.5\(1\)su9
Unified Communications ManagerApplication
Affected:>= 10.5\(2\), < 11.5\(1\)su9>= 12.0\(1\), < 12.5\(1\)su4
Unified Communications Manager Im \& Presence ServiceApplication
Affected:>= 10.5\(2\), < 11.5\(1\)su9>= 12.0\(1\), < 12.5\(1\)su4
Unity ConnectionApplication
Affected:>= 10.5\(2\), < 11.5\(1\)su9>= 12.0\(1\), < 12.5\(1\)su4

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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. Identify installed Cisco product
    Run 'show version' or check the application directory for one of: Cisco Prime License Manager, Cisco Unified Communications Manager, Cisco Unified Communications Manager IM & Presence Service, or Unity Connection
    Affected if The product matches one of the four affected products
  2. Check product version
    Run 'show version' or access the admin interface to view the installed version number
    Affected if The version falls within any of these ranges: 10.5(2) to 11.5(1)su8, 12.0(1) to 12.5(1)su3 (note: versions 11.5(1)su9 and 12.5(1)su4 and later are not affected)
  3. Verify SOAP API endpoint status
    Check the product administration interface or run 'admin show risdb' command to see if the SOAP API service is enabled
    Affected if SOAP API is enabled and accessible (the vulnerability requires the SOAP API endpoint to be reachable)
  4. Review access logs for SOAP API
    Examine SOAP API access logs in /var/log/soap/ or through the Real-Time Monitoring Tool for unusual or suspicious SOAP request patterns
    Affected if Log entries show unexpected SOAP requests with unusual parameters or commands not initiated by authorized administrators

You are affected if you run any of the four listed products, your version is within the vulnerable ranges, and the SOAP API endpoint is enabled and reachable on your network.

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.

dbcve · scoped
Upgrade available Upgrade to 11.5 / 12.5 or later
Fixed in 11.512.5
Interim mitigation

Apply Cisco's official security patches for CVE-2021-1362 to all affected products. Until patched, restrict network access to SOAP API endpoints and monitor for suspicious SOAP requests with unusual parameters.

Recommended fix High confidence

For 10.5(2)-11.5(1) range: upgrade to 11.5(1)su9 or later | For 12.0(1)-12.5(1) range: upgrade to 12.5(1)su4 or later

  1. Identify the specific Cisco product (CUCM, CUCM IM&P, Unity Connection, or Prime License Manager) and current version from the affected version ranges
  2. For Prime License Manager, CUCM, CUCM IM&P, or Unity Connection versions 10.5(2) through 11.5(1), plan upgrade to version 11.5(1)su9 or later
  3. For CUCM, CUCM IM&P, or Unity Connection versions 12.0(1) through 12.5(1), plan upgrade to version 12.5(1)su4 or later
  4. Review Cisco release notes for the target version for any special upgrade instructions
  5. Perform a full backup of the system before upgrading
  6. Execute the upgrade following Cisco's standard upgrade procedures for the specific product
  7. Verify the version after upgrade matches the fixed release (11.5(1)su9+ or 12.5(1)su4+)
  8. Test SOAP API functionality to confirm the vulnerability is remediated
Caveat Major version upgrades may require compatibility checks with adjacent systems and UC applications; review Cisco upgrade guides for detailed prerequisites

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Prime License Manager Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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