CVE-2024-53979 (GCVE-0-2024-53979)
Vulnerability from cvelistv5 – Published: 2024-11-29 18:50 – Updated: 2024-12-04 17:19
VLAI?
Title
Ansible collection "ibm.ibm_zhmc" has passwords in clear text in log file and in output of some modules when specified as input
Summary
ibm.ibm_zhmc is an Ansible collection for the IBM Z HMC. 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 module in the following cases: 1. The 'boot_ftp_password' and 'ssc_master_pw' properties are passed as input to the zhmc_partition Ansible module. 2. The 'ssc_master_pw' and 'zaware_master_pw' properties are passed as input to the zhmc_lpar Ansible module. 3. The 'password' property is passed as input to the zhmc_user Ansible module (just in log file, not in module output). 4. 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 retrieving facts for the corresponding resources. These properties appear in the log file only when the "log_file" module input parameter is used. By default, no log file is created. This issue has been fixed in ibm.ibm_zhmc version 1.9.3. Users are advised to upgrade. There are no known workarounds for this vulnerability.
Severity ?
8.3 (High)
CWE
- CWE-312 - Cleartext Storage of Sensitive Information
Assigner
References
| URL | Tags | |||||||
|---|---|---|---|---|---|---|---|---|
|
||||||||
Impacted products
| Vendor | Product | Version | ||
|---|---|---|---|---|
| zhmcclient | zhmc-ansible-modules |
Affected:
< 1.9.3
|
{
"containers": {
"adp": [
{
"affected": [
{
"cpes": [
"cpe:2.3:a:ibm:zhmc:*:*:*:*:*:*:*:*"
],
"defaultStatus": "unknown",
"product": "zhmc",
"vendor": "ibm",
"versions": [
{
"lessThan": "1.9.3",
"status": "affected",
"version": "0",
"versionType": "custom"
}
]
}
],
"metrics": [
{
"other": {
"content": {
"id": "CVE-2024-53979",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2024-12-04T17:15:37.730258Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2024-12-04T17:19:36.207Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"product": "zhmc-ansible-modules",
"vendor": "zhmcclient",
"versions": [
{
"status": "affected",
"version": "\u003c 1.9.3"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "ibm.ibm_zhmc is an Ansible collection for the IBM Z HMC. 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 module in the following cases: 1. The \u0027boot_ftp_password\u0027 and \u0027ssc_master_pw\u0027 properties are passed as input to the zhmc_partition Ansible module. 2. The \u0027ssc_master_pw\u0027 and \u0027zaware_master_pw\u0027 properties are passed as input to the zhmc_lpar Ansible module. 3. The \u0027password\u0027 property is passed as input to the zhmc_user Ansible module (just in log file, not in module output). 4. The \u0027bind_password\u0027 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 retrieving facts for the corresponding resources. These properties appear in the log file only when the \"log_file\" module input parameter is used. By default, no log file is created. This issue has been fixed in ibm.ibm_zhmc version 1.9.3. Users are advised to upgrade. There are no known workarounds for this vulnerability."
}
],
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 8.3,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "HIGH",
"scope": "CHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H",
"version": "3.1"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-312",
"description": "CWE-312: Cleartext Storage of Sensitive Information",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2024-11-29T18:50:31.398Z",
"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"shortName": "GitHub_M"
},
"references": [
{
"name": "https://github.com/zhmcclient/zhmc-ansible-modules/security/advisories/GHSA-mw6c-f428-jx4f",
"tags": [
"x_refsource_CONFIRM"
],
"url": "https://github.com/zhmcclient/zhmc-ansible-modules/security/advisories/GHSA-mw6c-f428-jx4f"
},
{
"name": "https://github.com/zhmcclient/zhmc-ansible-modules/commit/f5579f07da5f02d2496c41a313d4ae7a0a459b1d",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/zhmcclient/zhmc-ansible-modules/commit/f5579f07da5f02d2496c41a313d4ae7a0a459b1d"
}
],
"source": {
"advisory": "GHSA-mw6c-f428-jx4f",
"discovery": "UNKNOWN"
},
"title": "Ansible collection \"ibm.ibm_zhmc\" has passwords in clear text in log file and in output of some modules when specified as input"
}
},
"cveMetadata": {
"assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"assignerShortName": "GitHub_M",
"cveId": "CVE-2024-53979",
"datePublished": "2024-11-29T18:50:31.398Z",
"dateReserved": "2024-11-25T23:14:36.379Z",
"dateUpdated": "2024-12-04T17:19:36.207Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.1",
"vulnerability-lookup:meta": {
"fkie_nvd": {
"descriptions": "[{\"lang\": \"en\", \"value\": \"ibm.ibm_zhmc is an Ansible collection for the IBM Z HMC. 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 module in the following cases: 1. The \u0027boot_ftp_password\u0027 and \u0027ssc_master_pw\u0027 properties are passed as input to the zhmc_partition Ansible module. 2. The \u0027ssc_master_pw\u0027 and \u0027zaware_master_pw\u0027 properties are passed as input to the zhmc_lpar Ansible module. 3. The \u0027password\u0027 property is passed as input to the zhmc_user Ansible module (just in log file, not in module output). 4. The \u0027bind_password\u0027 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 retrieving facts for the corresponding resources. These properties appear in the log file only when the \\\"log_file\\\" module input parameter is used. By default, no log file is created. This issue has been fixed in ibm.ibm_zhmc version 1.9.3. Users are advised to upgrade. There are no known workarounds for this vulnerability.\"}, {\"lang\": \"es\", \"value\": \"ibm.ibm_zhmc es una colecci\\u00f3n de Ansible para IBM Z HMC. La colecci\\u00f3n de Ansible \\\"ibm.ibm_zhmc\\\" escribe propiedades similares a contrase\\u00f1as en texto sin formato en su archivo de registro y en la salida devuelta por algunos de sus m\\u00f3dulos de Ansible en los siguientes casos: 1. Las propiedades \u0027boot_ftp_password\u0027 y \u0027ssc_master_pw\u0027 se pasan como entrada al m\\u00f3dulo de Ansible zhmc_partition. 2. Las propiedades \u0027ssc_master_pw\u0027 y \u0027zaware_master_pw\u0027 se pasan como entrada al m\\u00f3dulo de Ansible zhmc_lpar. 3. La propiedad \u0027password\u0027 se pasa como entrada al m\\u00f3dulo de Ansible zhmc_user (solo en el archivo de registro, no en la salida del m\\u00f3dulo). 4. La propiedad \u0027bind_password\u0027 se pasa como entrada al m\\u00f3dulo de Ansible zhmc_ldap_server_definition. Estas propiedades aparecen en la salida del m\\u00f3dulo solo cuando se especificaron en la entrada del m\\u00f3dulo y al crear o actualizar los recursos correspondientes. No aparecen en la salida cuando se recuperan datos para los recursos correspondientes. Estas propiedades aparecen en el archivo de registro solo cuando se utiliza el par\\u00e1metro de entrada del m\\u00f3dulo \\\"log_file\\\". De forma predeterminada, no se crea ning\\u00fan archivo de registro. Este problema se ha solucionado en la versi\\u00f3n 1.9.3 de ibm.ibm_zhmc. Se recomienda a los usuarios que actualicen. No existen workarounds conocidos para esta vulnerabilidad.\"}]",
"id": "CVE-2024-53979",
"lastModified": "2024-11-29T19:15:09.847",
"metrics": "{\"cvssMetricV31\": [{\"source\": \"security-advisories@github.com\", \"type\": \"Secondary\", \"cvssData\": {\"version\": \"3.1\", \"vectorString\": \"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H\", \"baseScore\": 8.2, \"baseSeverity\": \"HIGH\", \"attackVector\": \"LOCAL\", \"attackComplexity\": \"LOW\", \"privilegesRequired\": \"HIGH\", \"userInteraction\": \"NONE\", \"scope\": \"CHANGED\", \"confidentialityImpact\": \"HIGH\", \"integrityImpact\": \"HIGH\", \"availabilityImpact\": \"HIGH\"}, \"exploitabilityScore\": 1.5, \"impactScore\": 6.0}]}",
"published": "2024-11-29T19:15:09.847",
"references": "[{\"url\": \"https://github.com/zhmcclient/zhmc-ansible-modules/commit/f5579f07da5f02d2496c41a313d4ae7a0a459b1d\", \"source\": \"security-advisories@github.com\"}, {\"url\": \"https://github.com/zhmcclient/zhmc-ansible-modules/security/advisories/GHSA-mw6c-f428-jx4f\", \"source\": \"security-advisories@github.com\"}]",
"sourceIdentifier": "security-advisories@github.com",
"vulnStatus": "Awaiting Analysis",
"weaknesses": "[{\"source\": \"security-advisories@github.com\", \"type\": \"Secondary\", \"description\": [{\"lang\": \"en\", \"value\": \"CWE-312\"}]}]"
},
"nvd": "{\"cve\":{\"id\":\"CVE-2024-53979\",\"sourceIdentifier\":\"security-advisories@github.com\",\"published\":\"2024-11-29T19:15:09.847\",\"lastModified\":\"2024-11-29T19:15:09.847\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"ibm.ibm_zhmc is an Ansible collection for the IBM Z HMC. 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 module in the following cases: 1. The \u0027boot_ftp_password\u0027 and \u0027ssc_master_pw\u0027 properties are passed as input to the zhmc_partition Ansible module. 2. The \u0027ssc_master_pw\u0027 and \u0027zaware_master_pw\u0027 properties are passed as input to the zhmc_lpar Ansible module. 3. The \u0027password\u0027 property is passed as input to the zhmc_user Ansible module (just in log file, not in module output). 4. The \u0027bind_password\u0027 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 retrieving facts for the corresponding resources. These properties appear in the log file only when the \\\"log_file\\\" module input parameter is used. By default, no log file is created. This issue has been fixed in ibm.ibm_zhmc version 1.9.3. Users are advised to upgrade. There are no known workarounds for this vulnerability.\"},{\"lang\":\"es\",\"value\":\"ibm.ibm_zhmc es una colecci\u00f3n de Ansible para IBM Z HMC. La colecci\u00f3n de Ansible \\\"ibm.ibm_zhmc\\\" escribe propiedades similares a contrase\u00f1as en texto sin formato en su archivo de registro y en la salida devuelta por algunos de sus m\u00f3dulos de Ansible en los siguientes casos: 1. Las propiedades \u0027boot_ftp_password\u0027 y \u0027ssc_master_pw\u0027 se pasan como entrada al m\u00f3dulo de Ansible zhmc_partition. 2. Las propiedades \u0027ssc_master_pw\u0027 y \u0027zaware_master_pw\u0027 se pasan como entrada al m\u00f3dulo de Ansible zhmc_lpar. 3. La propiedad \u0027password\u0027 se pasa como entrada al m\u00f3dulo de Ansible zhmc_user (solo en el archivo de registro, no en la salida del m\u00f3dulo). 4. La propiedad \u0027bind_password\u0027 se pasa como entrada al m\u00f3dulo de Ansible zhmc_ldap_server_definition. Estas propiedades aparecen en la salida del m\u00f3dulo solo cuando se especificaron en la entrada del m\u00f3dulo y al crear o actualizar los recursos correspondientes. No aparecen en la salida cuando se recuperan datos para los recursos correspondientes. Estas propiedades aparecen en el archivo de registro solo cuando se utiliza el par\u00e1metro de entrada del m\u00f3dulo \\\"log_file\\\". De forma predeterminada, no se crea ning\u00fan archivo de registro. Este problema se ha solucionado en la versi\u00f3n 1.9.3 de ibm.ibm_zhmc. Se recomienda a los usuarios que actualicen. No existen workarounds conocidos para esta vulnerabilidad.\"}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"security-advisories@github.com\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H\",\"baseScore\":8.2,\"baseSeverity\":\"HIGH\",\"attackVector\":\"LOCAL\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"HIGH\",\"userInteraction\":\"NONE\",\"scope\":\"CHANGED\",\"confidentialityImpact\":\"HIGH\",\"integrityImpact\":\"HIGH\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":1.5,\"impactScore\":6.0}]},\"weaknesses\":[{\"source\":\"security-advisories@github.com\",\"type\":\"Secondary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-312\"}]}],\"references\":[{\"url\":\"https://github.com/zhmcclient/zhmc-ansible-modules/commit/f5579f07da5f02d2496c41a313d4ae7a0a459b1d\",\"source\":\"security-advisories@github.com\"},{\"url\":\"https://github.com/zhmcclient/zhmc-ansible-modules/security/advisories/GHSA-mw6c-f428-jx4f\",\"source\":\"security-advisories@github.com\"}]}}",
"vulnrichment": {
"containers": "{\"adp\": [{\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2024-53979\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"total\"}], \"version\": \"2.0.3\", \"timestamp\": \"2024-12-04T17:15:37.730258Z\"}}}], \"affected\": [{\"cpes\": [\"cpe:2.3:a:ibm:zhmc:*:*:*:*:*:*:*:*\"], \"vendor\": \"ibm\", \"product\": \"zhmc\", \"versions\": [{\"status\": \"affected\", \"version\": \"0\", \"lessThan\": \"1.9.3\", \"versionType\": \"custom\"}], \"defaultStatus\": \"unknown\"}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2024-12-04T17:19:29.767Z\"}}], \"cna\": {\"title\": \"Ansible collection \\\"ibm.ibm_zhmc\\\" has passwords in clear text in log file and in output of some modules when specified as input\", \"source\": {\"advisory\": \"GHSA-mw6c-f428-jx4f\", \"discovery\": \"UNKNOWN\"}, \"metrics\": [{\"cvssV3_1\": {\"scope\": \"CHANGED\", \"version\": \"3.1\", \"baseScore\": 8.3, \"attackVector\": \"LOCAL\", \"baseSeverity\": \"HIGH\", \"vectorString\": \"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H\", \"integrityImpact\": \"HIGH\", \"userInteraction\": \"NONE\", \"attackComplexity\": \"LOW\", \"availabilityImpact\": \"HIGH\", \"privilegesRequired\": \"HIGH\", \"confidentialityImpact\": \"HIGH\"}}], \"affected\": [{\"vendor\": \"zhmcclient\", \"product\": \"zhmc-ansible-modules\", \"versions\": [{\"status\": \"affected\", \"version\": \"\u003c 1.9.3\"}]}], \"references\": [{\"url\": \"https://github.com/zhmcclient/zhmc-ansible-modules/security/advisories/GHSA-mw6c-f428-jx4f\", \"name\": \"https://github.com/zhmcclient/zhmc-ansible-modules/security/advisories/GHSA-mw6c-f428-jx4f\", \"tags\": [\"x_refsource_CONFIRM\"]}, {\"url\": \"https://github.com/zhmcclient/zhmc-ansible-modules/commit/f5579f07da5f02d2496c41a313d4ae7a0a459b1d\", \"name\": \"https://github.com/zhmcclient/zhmc-ansible-modules/commit/f5579f07da5f02d2496c41a313d4ae7a0a459b1d\", \"tags\": [\"x_refsource_MISC\"]}], \"descriptions\": [{\"lang\": \"en\", \"value\": \"ibm.ibm_zhmc is an Ansible collection for the IBM Z HMC. 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 module in the following cases: 1. The \u0027boot_ftp_password\u0027 and \u0027ssc_master_pw\u0027 properties are passed as input to the zhmc_partition Ansible module. 2. The \u0027ssc_master_pw\u0027 and \u0027zaware_master_pw\u0027 properties are passed as input to the zhmc_lpar Ansible module. 3. The \u0027password\u0027 property is passed as input to the zhmc_user Ansible module (just in log file, not in module output). 4. The \u0027bind_password\u0027 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 retrieving facts for the corresponding resources. These properties appear in the log file only when the \\\"log_file\\\" module input parameter is used. By default, no log file is created. This issue has been fixed in ibm.ibm_zhmc version 1.9.3. Users are advised to upgrade. There are no known workarounds for this vulnerability.\"}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-312\", \"description\": \"CWE-312: Cleartext Storage of Sensitive Information\"}]}], \"providerMetadata\": {\"orgId\": \"a0819718-46f1-4df5-94e2-005712e83aaa\", \"shortName\": \"GitHub_M\", \"dateUpdated\": \"2024-11-29T18:50:31.398Z\"}}}",
"cveMetadata": "{\"cveId\": \"CVE-2024-53979\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2024-12-04T17:19:36.207Z\", \"dateReserved\": \"2024-11-25T23:14:36.379Z\", \"assignerOrgId\": \"a0819718-46f1-4df5-94e2-005712e83aaa\", \"datePublished\": \"2024-11-29T18:50:31.398Z\", \"assignerShortName\": \"GitHub_M\"}",
"dataType": "CVE_RECORD",
"dataVersion": "5.1"
}
}
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…