CVE Vulnerabilities


Use of Hard-coded Credentials

Published: Jun 05, 2019 | Modified: Jun 06, 2019
CVSS 3.x
CVSS 2.x

A remote code execution vulnerability was identified in HPE Intelligent Management Center (IMC) PLAT earlier than version 7.3 E0506P09.


The product contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data.

Affected Software

Name Vendor Start Version End Version
Intelligent_management_center Hp * 7.3 (excluding)
Intelligent_management_center Hp 7.3 (including) 7.3 (including)
Intelligent_management_center Hp 7.3-e0503 (including) 7.3-e0503 (including)
Intelligent_management_center Hp 7.3-e0504 (including) 7.3-e0504 (including)
Intelligent_management_center Hp 7.3-e0504p02 (including) 7.3-e0504p02 (including)
Intelligent_management_center Hp 7.3-e0504p04 (including) 7.3-e0504p04 (including)
Intelligent_management_center Hp 7.3-e0506 (including) 7.3-e0506 (including)
Intelligent_management_center Hp 7.3-e0506p03 (including) 7.3-e0506p03 (including)
Intelligent_management_center Hp 7.3-e0506p07 (including) 7.3-e0506p07 (including)

Extended Description

Hard-coded credentials typically create a significant hole that allows an attacker to bypass the authentication that has been configured by the product administrator. This hole might be difficult for the system administrator to detect. Even if detected, it can be difficult to fix, so the administrator may be forced into disabling the product entirely. There are two main variations:

In the Inbound variant, a default administration account is created, and a simple password is hard-coded into the product and associated with that account. This hard-coded password is the same for each installation of the product, and it usually cannot be changed or disabled by system administrators without manually modifying the program, or otherwise patching the product. If the password is ever discovered or published (a common occurrence on the Internet), then anybody with knowledge of this password can access the product. Finally, since all installations of the product will have the same password, even across different organizations, this enables massive attacks such as worms to take place. The Outbound variant applies to front-end systems that authenticate with a back-end service. The back-end service may require a fixed password which can be easily discovered. The programmer may simply hard-code those back-end credentials into the front-end product. Any user of that program may be able to extract the password. Client-side systems with hard-coded passwords pose even more of a threat, since the extraction of a password from a binary is usually very simple.

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.