CVE Vulnerabilities

CVE-2020-11854

Use of Hard-coded Credentials

Published: Oct 27, 2020 | Modified: Nov 21, 2024
CVSS 3.x
9.8
CRITICAL
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS 2.x
10 HIGH
AV:N/AC:L/Au:N/C:C/I:C/A:C
RedHat/V2
RedHat/V3
Ubuntu

Arbitrary code execution vlnerability in Operation bridge Manager, Application Performance Management and Operations Bridge (containerized) vulnerability in Micro Focus products products Operation Bridge Manager, Operation Bridge (containerized) and Application Performance Management. The vulneravility affects: 1.) Operation Bridge Manager versions 2020.05, 2019.11, 2019.05, 2018.11, 2018.05, 10.63,10.62, 10.61, 10.60, 10.12, 10.11, 10.10 and all earlier versions. 2.) Operations Bridge (containerized) 2020.05, 2019.08, 2019.05, 2018.11, 2018.08, 2018.05. 2018.02 and 2017.11. 3.) Application Performance Management versions 9,51, 9.50 and 9.40 with uCMDB 10.33 CUP 3. The vulnerability could allow Arbitrary code execution.

Weakness

The product contains hard-coded credentials, such as a password or cryptographic key.

Affected Software

Name Vendor Start Version End Version
Application_performance_management Microfocus 9.50 (including) 9.50 (including)
Application_performance_management Microfocus 9.51 (including) 9.51 (including)
Operations_bridge Microfocus 2017.11 (including) 2017.11 (including)
Operations_bridge Microfocus 2018.02 (including) 2018.02 (including)
Operations_bridge Microfocus 2018.05 (including) 2018.05 (including)
Operations_bridge Microfocus 2018.08 (including) 2018.08 (including)
Operations_bridge Microfocus 2018.11 (including) 2018.11 (including)
Operations_bridge Microfocus 2019.05 (including) 2019.05 (including)
Operations_bridge Microfocus 2019.08 (including) 2019.08 (including)
Operations_bridge Microfocus 2020.05 (including) 2020.05 (including)
Operations_bridge_manager Microfocus * 10.10 (including)
Operations_bridge_manager Microfocus 10.11 (including) 10.11 (including)
Operations_bridge_manager Microfocus 10.12 (including) 10.12 (including)
Operations_bridge_manager Microfocus 10.60 (including) 10.60 (including)
Operations_bridge_manager Microfocus 10.61 (including) 10.61 (including)
Operations_bridge_manager Microfocus 10.62 (including) 10.62 (including)
Operations_bridge_manager Microfocus 10.63 (including) 10.63 (including)
Operations_bridge_manager Microfocus 2018.05 (including) 2018.05 (including)
Operations_bridge_manager Microfocus 2018.11 (including) 2018.11 (including)
Operations_bridge_manager Microfocus 2019.05 (including) 2019.05 (including)
Operations_bridge_manager Microfocus 2019.11 (including) 2019.11 (including)
Operations_bridge_manager Microfocus 2020.05 (including) 2020.05 (including)

Extended Description

There are two main variations:

Potential Mitigations

  • For outbound authentication: store passwords, keys, and other credentials outside of the code in a strongly-protected, encrypted configuration file or database that is protected from access by all outsiders, including other local users on the same system. Properly protect the key (CWE-320). If you cannot use encryption to protect the file, then make sure that the permissions are as restrictive as possible [REF-7].
  • In Windows environments, the Encrypted File System (EFS) may provide some protection.
  • For inbound authentication using passwords: apply strong one-way hashes to passwords and store those hashes in a configuration file or database with appropriate access control. That way, theft of the file/database still requires the attacker to try to crack the password. When handling an incoming password during authentication, take the hash of the password and compare it to the saved hash.
  • Use randomly assigned salts for each separate hash that is generated. This increases the amount of computation that an attacker needs to conduct a brute-force attack, possibly limiting the effectiveness of the rainbow table method.
  • For front-end to back-end connections: Three solutions are possible, although none are complete.

References