January 2, 2020
Cisco Data Center Network Manager is prone to multiple SQL-injection vulnerabilities because it fails to sufficiently sanitize user-supplied data before using it in an SQL query. Exploiting these issues could allow an attacker to compromise the application, access or modify data or exploit latent vulnerabilities in the underlying database. These issues are being tracked by Cisco Bug IDs CSCvq98723, CSCvq98730, CSCvq98736, CSCvq98748, CSCvr01692, CSCvr01694, CSCvr01701, CSCvr07317, CSCvr14598, CSCvr17974, CSCvr23573, CSCvr23728, CSCvr23733, CSCvr23770, CSCvr23864, CSCvr23865, CSCvr32014, CSCvr34624, CSCvr46544, CSCvr46547, CSCvr79116, CSCvr79127 and CSCvs16306. Cisco Data Center Network Manager versions prior to 11.3(1) are vulnerable.
- Cisco Data Center Network Manager 10.0(1)
- Cisco Data Center Network Manager 10.1(1)
- Cisco Data Center Network Manager 10.2(1)
- Cisco Data Center Network Manager 10.3(1)
- Cisco Data Center Network Manager 10.4(1)
- Cisco Data Center Network Manager 10.4(2)
- Cisco Data Center Network Manager 11.0(1)
- Cisco Data Center Network Manager 11.1(1)
- Cisco Data Center Network Manager 11.2(1)
- Cisco Data Center Network Manager 5.2(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.
Steven Seeley (mr_me) of Source Incite, working with Trend Micro’s Zero Day Initiative and iDefense and Accenture
© 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 firstname.lastname@example.org.
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 email@example.com 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.