Cisco Unified Communications Manager CVE-2019-15972 SQL Injection Vulnerability



Date Discovered

November 20, 2019


Cisco Unified Communications Manager is prone to an SQL-injection vulnerability because it fails to sufficiently sanitize user-supplied data before using it in an SQL query. Exploiting this issue could allow an attacker to compromise the application, access or modify data, or exploit latent vulnerabilities in the underlying database. This issue being tracked by Cisco Bug ID CSCvp49463. Cisco Unified Communications Manager version prior to 11.5(1)SU6 and 12.5(1)SU1 are vulnerable.

Technologies Affected

  • Cisco Unified Communications Manager 11.5
  • Cisco Unified Communications Manager 11.5(0.98000.480)
  • Cisco Unified Communications Manager 11.5(1)SU5
  • Cisco Unified Communications Manager 12.5
  • Cisco Unified Communications Manager 12.5(0.98000.666)
  • Cisco Unified Communications Manager 12.5(0.98000.667)
  • Cisco Unified Communications Manager 12.5(1)


Block external access at the network boundary, unless external parties require service.
Filter access to the affected computer at the network boundary if global access isn't needed. Restricting access to only trusted computers and networks might greatly reduce the likelihood of a successful exploit.

Deploy network intrusion detection systems to monitor network traffic for malicious activity.
Deploy NIDS to monitor network traffic for signs of anomalous or suspicious activity including unexplained incoming and outgoing traffic. This may indicate exploit attempts or activity that results from successful exploits.

Run all software as a nonprivileged user with minimal access rights.
To limit the consequences of successful exploits, run server processes within a restricted environment using facilities such as chroot or jail.

Modify default ACL settings.
Implement database access control to limit the immediate impact of such vulnerabilities on the data within the database and possibly the database itself. Ensure that applications are isolated from one another and from sensitive data in the database through separate user accounts and restrictive ACL configurations.

Updates are available. Please see the references or vendor advisory for more information.



Ken Gannon and Vahe Demirkhanyan of F-Secure

© 1995- Symantec Corporation

Permission to redistribute this alert electronically is granted as long as it is not edited in any way unless authorized by Symantec Security Response. Reprinting the whole or part of this alert in any medium other than electronically requires permission from


The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.

Symantec, Symantec products, Symantec Security Response, and are registered trademarks of Symantec Corp. and/or affiliated companies in the United States and other countries. All other registered and unregistered trademarks represented in this document are the sole property of their respective companies/owners.