GHSA-4r65-35qq-ch8j
Vulnerability from github
Published
2022-03-04 00:00
Modified
2024-09-09 21:00
Summary
Ansible discloses sensitive information in traceback error message
Details

Ansible is an IT automation system that handles configuration management, application deployment, cloud provisioning, ad-hoc task execution, network automation, and multi-node orchestration. A flaw was found in Ansible Engine's ansible-connection module where sensitive information, such as the Ansible user credentials, is disclosed by default in the traceback error message when Ansible receives an unexpected response from set_options. The highest threat from this vulnerability is confidentiality.

Show details on source website


{
   affected: [
      {
         package: {
            ecosystem: "PyPI",
            name: "ansible",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "0",
                  },
                  {
                     fixed: "2.9.27",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
   ],
   aliases: [
      "CVE-2021-3620",
   ],
   database_specific: {
      cwe_ids: [
         "CWE-209",
      ],
      github_reviewed: true,
      github_reviewed_at: "2022-03-24T21:40:53Z",
      nvd_published_at: "2022-03-03T19:15:00Z",
      severity: "MODERATE",
   },
   details: "Ansible is an IT automation system that handles configuration management, application deployment, cloud provisioning, ad-hoc task execution, network automation, and multi-node orchestration. A flaw was found in Ansible Engine's ansible-connection module where sensitive information, such as the Ansible user credentials, is disclosed by default in the traceback error message when Ansible receives an unexpected response from `set_options`. The highest threat from this vulnerability is confidentiality.",
   id: "GHSA-4r65-35qq-ch8j",
   modified: "2024-09-09T21:00:59Z",
   published: "2022-03-04T00:00:17Z",
   references: [
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2021-3620",
      },
      {
         type: "WEB",
         url: "https://github.com/ansible/ansible/commit/fe28767970c8ec62aabe493c46b53a5de1e5fac0",
      },
      {
         type: "WEB",
         url: "https://access.redhat.com/errata/RHSA-2021:3871",
      },
      {
         type: "WEB",
         url: "https://access.redhat.com/errata/RHSA-2021:3872",
      },
      {
         type: "WEB",
         url: "https://access.redhat.com/errata/RHSA-2021:3874",
      },
      {
         type: "WEB",
         url: "https://access.redhat.com/errata/RHSA-2021:4703",
      },
      {
         type: "WEB",
         url: "https://access.redhat.com/errata/RHSA-2021:4750",
      },
      {
         type: "WEB",
         url: "https://access.redhat.com/security/cve/CVE-2021-3620",
      },
      {
         type: "WEB",
         url: "https://bugzilla.redhat.com/show_bug.cgi?id=1975767",
      },
      {
         type: "ADVISORY",
         url: "https://github.com/advisories/GHSA-4r65-35qq-ch8j",
      },
      {
         type: "PACKAGE",
         url: "https://github.com/ansible/ansible",
      },
      {
         type: "WEB",
         url: "https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.9.rst#security-fixes",
      },
      {
         type: "WEB",
         url: "https://github.com/pypa/advisory-database/tree/main/vulns/ansible/PYSEC-2022-164.yaml",
      },
      {
         type: "WEB",
         url: "https://lists.debian.org/debian-lts-announce/2023/12/msg00018.html",
      },
   ],
   schema_version: "1.4.0",
   severity: [
      {
         score: "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
         type: "CVSS_V3",
      },
      {
         score: "CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N",
         type: "CVSS_V4",
      },
   ],
   summary: "Ansible discloses sensitive information in traceback error message",
}


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.


Loading…

Loading…

Loading…

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.