Vulnerabilities
Misconfiguration
Compliance
CVE Vulnerabilities

CVE-2020-4932

Use of Hard-coded Credentials

Published: May 05, 2021 | Modified: Nov 21, 2024
CVSS 3.x
7.8
HIGH
Source:
NVD
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS 2.x
4.6 MEDIUM
AV:L/AC:L/Au:N/C:P/I:P/A:P
RedHat/V2
RedHat/V3
Ubuntu
Vulnerability-free packages from our partners
Additional information
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2020-4932
CWEhttps://cwe.mitre.org/data/definitions/798.html

IBM QRadar SIEM 7.3 and 7.4 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. IBM X-Force ID: 191748.

Weakness

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

Affected Software

Name Vendor Start Version End Version
Qradar_security_information_and_event_manager Ibm 7.3.0 (including) 7.3.3 (excluding)
Qradar_security_information_and_event_manager Ibm 7.4.0 (including) 7.4.2 (excluding)
Qradar_security_information_and_event_manager Ibm 7.3.3 (including) 7.3.3 (including)
Qradar_security_information_and_event_manager Ibm 7.3.3-fix_pack_1 (including) 7.3.3-fix_pack_1 (including)
Qradar_security_information_and_event_manager Ibm 7.3.3-fix_pack_2 (including) 7.3.3-fix_pack_2 (including)
Qradar_security_information_and_event_manager Ibm 7.3.3-fix_pack_3 (including) 7.3.3-fix_pack_3 (including)
Qradar_security_information_and_event_manager Ibm 7.3.3-fix_pack_4 (including) 7.3.3-fix_pack_4 (including)
Qradar_security_information_and_event_manager Ibm 7.3.3-fix_pack_5 (including) 7.3.3-fix_pack_5 (including)
Qradar_security_information_and_event_manager Ibm 7.3.3-fix_pack_6 (including) 7.3.3-fix_pack_6 (including)
Qradar_security_information_and_event_manager Ibm 7.3.3-fix_pack_7 (including) 7.3.3-fix_pack_7 (including)
Qradar_security_information_and_event_manager Ibm 7.4.2 (including) 7.4.2 (including)
Qradar_security_information_and_event_manager Ibm 7.4.2-fix_pack_1 (including) 7.4.2-fix_pack_1 (including)
Qradar_security_information_and_event_manager Ibm 7.4.2-fix_pack_2 (including) 7.4.2-fix_pack_2 (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

Aqua Security is the largest pure-play cloud native security company, providing customers the freedom to innovate and run their businesses with minimal friction. The Aqua Cloud Native Security Platform provides prevention, detection, and response automation across the entire application lifecycle to secure the build, secure cloud infrastructure and secure running workloads wherever they are deployed.
Copyright © 2025 Aqua Security Software Ltd.   Privacy Policy | Terms of Use