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

1/6/2020
10:35 AM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

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
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
Hacking Yourself: Marie Moe and Pacemaker Security
Gary McGraw Ph.D., Co-founder Berryville Institute of Machine Learning,  9/21/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15208
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a `DCHECK` which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can ...
CVE-2020-15209
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, a crafted TFLite model can force a node to have as input a tensor backed by a `nullptr` buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one....
CVE-2020-15210
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption. We have patched the issue in d58c96946b and ...
CVE-2020-15211
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indices f...
CVE-2020-15212
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor. Users having access to `segment_ids_data` can alter `output_index` and then write to outside of `outpu...