GHSA-p75j-wc34-527c
Vulnerability from github
Published
2021-10-12 16:31
Modified
2024-11-18 16:26
Severity ?
6.5 (Medium) - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
7.1 (High) - 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
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.

Show details on source website

To clipboard 

{
   affected: [
      {
         package: {
            ecosystem: "PyPI",
            name: "ansible",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "2.8.0a1",
                  },
                  {
                     fixed: "2.8.4",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
   ],
   aliases: [
      "CVE-2019-10217",
   ],
   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",
   },
   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.",
   id: "GHSA-p75j-wc34-527c",
   modified: "2024-11-18T16:26:16Z",
   published: "2021-10-12T16:31:59Z",
   references: [
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2019-10217",
      },
      {
         type: "WEB",
         url: "https://github.com/ansible/ansible/issues/56269",
      },
      {
         type: "WEB",
         url: "https://github.com/ansible/ansible/pull/59427",
      },
      {
         type: "WEB",
         url: "https://github.com/ansible/ansible/commit/c1ee1f142db1e669b710a65147ea32be47a91519",
      },
      {
         type: "WEB",
         url: "https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-10217",
      },
      {
         type: "ADVISORY",
         url: "https://github.com/advisories/GHSA-p75j-wc34-527c",
      },
      {
         type: "PACKAGE",
         url: "https://github.com/ansible/ansible",
      },
      {
         type: "WEB",
         url: "https://github.com/pypa/advisory-database/tree/main/vulns/ansible/PYSEC-2019-3.yaml",
      },
      {
         type: "WEB",
         url: "http://lists.opensuse.org/opensuse-security-announce/2020-04/msg00021.html",
      },
      {
         type: "WEB",
         url: "http://lists.opensuse.org/opensuse-security-announce/2020-04/msg00026.html",
      },
   ],
   schema_version: "1.4.0",
   severity: [
      {
         score: "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
         type: "CVSS_V3",
      },
      {
         score: "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",
         type: "CVSS_V4",
      },
   ],
   summary: "Exposure of Sensitive Information to an Unauthorized Actor in ansible",
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.