Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Network Security

10:35 AM
Larry Loeb
Larry Loeb
Larry Loeb

Why Cisco's DCNM Is in a World of Trouble

Vendor's Data Center Network Manager (DCNM) has racked up three critical authentication bypass vulnerabilities at the top of the list of 12 separate problems that were announced on January 2.

Cisco's Data Center Network Manager (DCNM) has been found to be in a world of trouble, racking up three critical authentication bypass vulnerabilities at the top of the list of 12 separate problems that were announced on January 2, 2020. These three have a CVSS of 9.8 out of 10, so they are serious.

Cisco says in a security advisory about the problems that the vulnerabilities "could allow an unauthenticated, remote attacker to bypass authentication and execute arbitrary actions with administrative privileges on an affected device."

While Cisco has released software updates that it says will address and fix the reported problems, there are "no workarounds that address these vulnerabilities."

These vulnerabilities affect Cisco DCNM software releases earlier than Release 11.3(1) for Microsoft Windows, Linux and virtual appliance platforms.

The vulnerabilities are said by Cisco to not be dependent on one another. That means that exploitation of one of the vulnerabilities is not required to exploit another vulnerability. Cisco also says that a software release which is affected by one of the vulnerabilities may not be affected by the other vulnerabilities.

One of the vulnerabilities (CVE-2019-15975) is in the REST API endpoint of Cisco DCNM. Cisco says that the vulnerability exists because "a static encryption key is shared between installations." That means that an attacker could exploit it by using the static key to craft a valid session token. A successful exploit could then allow the attacker to perform arbitrary actions by use of the REST API with administrative privileges.

CVE-2019-15976 is basically the same problem of a static key existing between installations, but in the SOAP API endpoint of Cisco DCNM. The same results of remote attack could occur through the use of a differing API than before.

A vulnerability (CVE-2019-15977) is also present in the web-based management interface of Cisco DCNM that could once again allow an unauthenticated, remote attacker to bypass authentication on an affected device.

This time it's the presence of static credentials causing the problem. An attacker could use the static credentials to authenticate malware that attacks through the user interface. A successful attack could then access a specific section of the web interface and obtain confidential information from an affected device. This information could be used in further attacks against the system.

The Cisco Product Security Incident Response Team (PSIRT) is not aware of any public announcements or malicious use of the vulnerabilities that they described in the advisory.

Security firm Tenable says that by utilizing these authentication bypass vulnerabilities, attackers could in their exploits leverage the remaining flaws patched by Cisco, which include command injection vulnerabilities (CVE-2019-15978, CVE-2019-15979), SQL injection vulnerabilities (CVE-2019-15984, CVE-2019-15985), path traversal vulnerabilities (CVE-2019-15980, CVE-15981, CVE-2019-15982) and an XML external entity vulnerability (CVE-2019-15983).

Eleven of the vulnerabilities were discovered and reported to Cisco by Steven Seeley of Source Incite. Cisco's software update also patched CVE-2019-15999, which is a vulnerability in the DCNM's JBoss Enterprise Application Platform (EAP) reported by Harrison Neal of PatchAdvisor. The authentication settings on the EAP were evidently incorrectly configured.

— Larry Loeb has written for many of the last century's major "dead tree" computer magazines, having been, among other things, a consulting editor for BYTE magazine and senior editor for the launch of WebWeek.

Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Current Issue
Enterprise Cybersecurity Plans in a Post-Pandemic World
Download the Enterprise Cybersecurity Plans in a Post-Pandemic World report to understand how security leaders are maintaining pace with pandemic-related challenges, and where there is room for improvement.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2021-09-17
nLight ECLYPSE (nECY) system Controllers running software prior to 1.17.21245.754 contain a default key vulnerability. The nECY does not force a change to the key upon the initial configuration of an affected device. nECY system controllers utilize an encrypted channel to secure SensorViewTM configu...
PUBLISHED: 2021-09-17
An issue was discovered in CMS Made Simple 2.2.8. It is possible to achieve unauthenticated path traversal in the CGExtensions module (in the file action.setdefaulttemplate.php) with the m1_filename parameter; and through the action.showmessage.php file, it is possible to read arbitrary file content...
PUBLISHED: 2021-09-17
Improper input validation in the National Instruments NI-PAL driver in versions 20.0.0 and prior may allow a privileged user to potentially enable escalation of privilege via local access.
PUBLISHED: 2021-09-17
XSS Hunter Express before 2021-09-17 does not properly enforce authentication requirements for paths.
PUBLISHED: 2021-09-17
The Device42 Remote Collector before 17.05.01 does not sanitize user input in its SNMP Connectivity utility. This allows an authenticated attacker (with access to the console application) to execute arbitrary OS commands and escalate privileges.