pysec-2020-2
Vulnerability from pysec
Published
2020-04-30 17:15
Modified
2020-05-21 14:49
Details

An archive traversal flaw was found in all ansible-engine versions 2.9.x prior to 2.9.7, when running ansible-galaxy collection install. When extracting a collection .tar.gz file, the directory is created without sanitizing the filename. An attacker could take advantage to overwrite any file within the system.

Impacted products
Name purl
ansible pkg:pypi/ansible
Aliases


To clipboard 

{
   affected: [
      {
         package: {
            ecosystem: "PyPI",
            name: "ansible",
            purl: "pkg:pypi/ansible",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "2.9.0",
                  },
                  {
                     fixed: "2.9.7",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
         versions: [
            "2.9.0",
            "2.9.1",
            "2.9.2",
            "2.9.3",
            "2.9.4",
            "2.9.5",
            "2.9.6",
         ],
      },
   ],
   aliases: [
      "CVE-2020-10691",
      "GHSA-3c67-gc48-983w",
   ],
   details: "An archive traversal flaw was found in all ansible-engine versions 2.9.x prior to 2.9.7, when running ansible-galaxy collection install. When extracting a collection .tar.gz file, the directory is created without sanitizing the filename. An attacker could take advantage to overwrite any file within the system.",
   id: "PYSEC-2020-2",
   modified: "2020-05-21T14:49:00Z",
   published: "2020-04-30T17:15:00Z",
   references: [
      {
         type: "REPORT",
         url: "https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-10691",
      },
      {
         type: "WEB",
         url: "https://github.com/ansible/ansible/pull/68596",
      },
      {
         type: "ADVISORY",
         url: "https://github.com/advisories/GHSA-3c67-gc48-983w",
      },
   ],
}


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.