Lucene search

K
symantecSymantec Security ResponseSMNTC-110325
HistoryOct 02, 2019 - 12:00 a.m.

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

2019-10-0200:00:00
Symantec Security Response
www.symantec.com
16

EPSS

0.002

Percentile

55.8%

Description

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 CSCvo42378.

Technologies Affected

  • Cisco Unified Communications Manager 10.5(2)
  • Cisco Unified Communications Manager 11.5(1)SU5
  • Cisco Unified Communications Manager 12.0(1)SU2
  • Cisco Unified Communications Manager 12.5(1)
  • Cisco Unified Communications Manager Session Management Edition (SME) 10.5(2)
  • Cisco Unified Communications Manager Session Management Edition (SME) 11.5(1)SU5
  • Cisco Unified Communications Manager Session Management Edition (SME) 12.0(1)SU2
  • Cisco Unified Communications Manager Session Management Edition (SME) 12.5(1)

Recommendations

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.

References

EPSS

0.002

Percentile

55.8%

Related for SMNTC-110325