Skip to content

Ansible collection "ibm.ibm_zhmc" has passwords in clear text in log file and in output of some modules when specified as input

High
andy-maier published GHSA-mw6c-f428-jx4f Nov 29, 2024

Package

ibm.ibm_zhmc (Ansible)

Affected versions

<1.9.3

Patched versions

1.9.3

Description

Impact

The Ansible collection "ibm.ibm_zhmc" writes password-like properties in clear text into its log file and into the output returned by some of its Ansible modules in the following cases:

  • The 'boot_ftp_password' or 'ssc_master_pw' properties are passed as input to the zhmc_partition Ansible module
  • The 'ssc_master_pw' or 'zaware_master_pw' properties are passed as input to the zhmc_lpar Ansible module
  • The 'password' property is passed as input to the zhmc_user Ansible module (just in log file, not in module output)
  • The 'bind_password' property is passed as input to the zhmc_ldap_server_definition Ansible module

These properties appear in the module output only when they were specified in the module input and when creating or updating the corresponding resources. They do not appear in the output when they were not specified in the module input or when retrieving facts for the corresponding resources.

A log file is created only when the "log_file" module input parameter of the Ansible modules is used. By default, no log file is created.

Patches

Has been fixed in ibm.ibm_zhmc version 1.9.3.

Workarounds

Not applicable, since fix is available.

References

None

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

CVE ID

No known CVE

Weaknesses

No CWEs

Credits