Количество 6
Количество 6
CVE-2019-10217
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.
CVE-2019-10217
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.
CVE-2019-10217
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.
CVE-2019-10217
A flaw was found in ansible 2.8.0 before 2.8.4. Fields managing sensit ...
GHSA-p75j-wc34-527c
Exposure of Sensitive Information to an Unauthorized Actor in ansible
openSUSE-SU-2020:0513-1
Security update for ansible
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
 | CVE-2019-10217 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. | CVSS3: 6.5 | 2% Низкий | почти 7 лет назад |
 | CVE-2019-10217 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. | CVSS3: 5.7 | 2% Низкий | около 7 лет назад |
 | CVE-2019-10217 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. | CVSS3: 6.5 | 2% Низкий | почти 7 лет назад |
| CVE-2019-10217 A flaw was found in ansible 2.8.0 before 2.8.4. Fields managing sensit ... | CVSS3: 6.5 | 2% Низкий | почти 7 лет назад |
| GHSA-p75j-wc34-527c Exposure of Sensitive Information to an Unauthorized Actor in ansible | CVSS3: 6.5 | 2% Низкий | почти 5 лет назад |
 | openSUSE-SU-2020:0513-1 Security update for ansible | больше 6 лет назад |
Уязвимостей на страницу