ID CVE-2020-3382
Summary A vulnerability in the REST API of Cisco Data Center Network Manager (DCNM) could allow an unauthenticated, remote attacker to bypass authentication and execute arbitrary actions with administrative privileges on an affected device. The vulnerability exists because different installations share a static encryption key. An attacker could exploit this vulnerability by using the static key to craft a valid session token. A successful exploit could allow the attacker to perform arbitrary actions through the REST API with administrative privileges.
References
Vulnerable Configurations
  • cpe:2.3:a:cisco:data_center_network_manager:4.0:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:data_center_network_manager:4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:data_center_network_manager:4.1:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:data_center_network_manager:4.1:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:data_center_network_manager:4.2:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:data_center_network_manager:4.2:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:data_center_network_manager:5.0:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:data_center_network_manager:5.0:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:data_center_network_manager:10.0:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:data_center_network_manager:10.0:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:data_center_network_manager:10.1:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:data_center_network_manager:10.1:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:data_center_network_manager:10.2\(1\):*:*:*:*:*:*:*
    cpe:2.3:a:cisco:data_center_network_manager:10.2\(1\):*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:data_center_network_manager:10.3\(1\):*:*:*:*:*:*:*
    cpe:2.3:a:cisco:data_center_network_manager:10.3\(1\):*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:data_center_network_manager:10.4\(1\):*:*:*:*:*:*:*
    cpe:2.3:a:cisco:data_center_network_manager:10.4\(1\):*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:data_center_network_manager:10.4\(2\):*:*:*:*:*:*:*
    cpe:2.3:a:cisco:data_center_network_manager:10.4\(2\):*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:data_center_network_manager:11.0\(1\):*:*:*:*:*:*:*
    cpe:2.3:a:cisco:data_center_network_manager:11.0\(1\):*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:data_center_network_manager:11.1\(1\):*:*:*:*:*:*:*
    cpe:2.3:a:cisco:data_center_network_manager:11.1\(1\):*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:data_center_network_manager:11.2\(1\):*:*:*:*:*:*:*
    cpe:2.3:a:cisco:data_center_network_manager:11.2\(1\):*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:data_center_network_manager:11.3\(1\):*:*:*:*:*:*:*
    cpe:2.3:a:cisco:data_center_network_manager:11.3\(1\):*:*:*:*:*:*:*
CVSS
Base: 10.0
Impact:
Exploitability:
CWE CWE-798
CAPEC
  • Read Sensitive Strings Within an Executable
    An adversary engages in activities to discover any sensitive strings are present within the compiled code of an executable, such as literal ASCII strings within the file itself, or possibly strings hard-coded into particular routines that can be revealed by code refactoring methods including static and dynamic analysis. One specific example of a sensitive string is a hard-coded password. Typical examples of software with hard-coded passwords include server-side executables which may check for a hard-coded password or key during a user's authentication with the server. Hard-coded passwords can also be present in client-side executables which utilize the password or key when connecting to either a remote component, such as a database server, licensing server, or otherwise, or a processes on the same host that expects a key or password. When analyzing an executable the adversary may search for the presence of such strings by analyzing the byte-code of the file itself. Example utilities for revealing strings within a file include 'strings,' 'grep,' or other variants of these programs depending upon the type of operating system used. These programs can be used to dump any ASCII or UNICODE strings contained within a program. Strings can also be searched for using a hex editors by loading the binary or object code file and utilizing native search functions such as regular expressions.
  • Try Common or Default Usernames and Passwords
    An adversary may try certain common or default usernames and passwords to gain access into the system and perform unauthorized actions. An adversary may try an intelligent brute force using empty passwords, known vendor default credentials, as well as a dictionary of common usernames and passwords. Many vendor products come preconfigured with default (and thus well-known) usernames and passwords that should be deleted prior to usage in a production environment. It is a common mistake to forget to remove these default login credentials. Another problem is that users would pick very simple (common) passwords (e.g. "secret" or "password") that make it easier for the attacker to gain access to the system compared to using a brute force attack or even a dictionary attack using a full dictionary.
Access
VectorComplexityAuthentication
NETWORK LOW NONE
Impact
ConfidentialityIntegrityAvailability
COMPLETE COMPLETE COMPLETE
Last major update 31-07-2020 - 01:15
Published 31-07-2020 - 00:15
Last modified 05-08-2020 - 14:18
Back to Top