GHSA-p75j-wc34-527c

Suggest an improvement
Source
https://github.com/advisories/GHSA-p75j-wc34-527c
Import Source
https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2021/10/GHSA-p75j-wc34-527c/GHSA-p75j-wc34-527c.json
JSON Data
https://api.osv.dev/v1/vulns/GHSA-p75j-wc34-527c
Aliases
Published
2021-10-12T16:31:59Z
Modified
2024-11-25T05:39:33Z
Severity
  • 6.5 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N CVSS Calculator
  • 7.1 (High) CVSS_V4 - CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N CVSS Calculator
Summary
Exposure of Sensitive Information to an Unauthorized Actor in ansible
Details

A flaw was found in ansible 2.8.0 before 2.8.4. Fields managing sensitive data should be set as such by no_log feature. Some of these fields in GCP modules are not set properly. service_account_contents() which is common class for all gcp modules is not setting no_log to True. Any sensitive data managed by that function would be leak as an output when running ansible playbooks.

Database specific
{
    "cwe_ids": [
        "CWE-200"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2021-10-08T23:04:41Z",
    "nvd_published_at": "2019-11-25T16:15:00Z",
    "severity": "HIGH"
}
References

Affected packages

PyPI / ansible

Package

Affected ranges

Type
ECOSYSTEM
Events
Introduced
2.8.0a1
Fixed
2.8.4

Affected versions

2.*
2.8.0a1
2.8.0b1
2.8.0rc1
2.8.0rc2
2.8.0rc3
2.8.0
2.8.1
2.8.2
2.8.3

Database specific

source
"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2021/10/GHSA-p75j-wc34-527c/GHSA-p75j-wc34-527c.json"