pysec-2018-43
Vulnerability from pysec
Published
2018-07-13 22:29
Modified
2021-07-02 02:41
Details

A flaw was found in ansible. ansible.cfg is read from the current working directory which can be altered to make it point to a plugin or a module path under the control of an attacker, thus allowing the attacker to execute arbitrary code.

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.5",
                  },
                  {
                     fixed: "2.5.6",
                  },
                  {
                     introduced: "2.4",
                  },
                  {
                     fixed: "2.4.6.0",
                  },
                  {
                     introduced: "2.6",
                  },
                  {
                     fixed: "2.6.1",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
         versions: [
            "2.4.0.0",
            "2.4.1.0",
            "2.4.2.0",
            "2.4.3.0",
            "2.4.4.0",
            "2.4.5.0",
            "2.5.0",
            "2.5.1",
            "2.5.2",
            "2.5.3",
            "2.5.4",
            "2.5.5",
            "2.6.0",
         ],
      },
   ],
   aliases: [
      "CVE-2018-10875",
   ],
   details: "A flaw was found in ansible. ansible.cfg is read from the current working directory which can be altered to make it point to a plugin or a module path under the control of an attacker, thus allowing the attacker to execute arbitrary code.",
   id: "PYSEC-2018-43",
   modified: "2021-07-02T02:41:34.153569Z",
   published: "2018-07-13T22:29:00Z",
   references: [
      {
         type: "REPORT",
         url: "https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-10875",
      },
      {
         type: "ADVISORY",
         url: "https://access.redhat.com/errata/RHSA-2018:2166",
      },
      {
         type: "ADVISORY",
         url: "https://access.redhat.com/errata/RHSA-2018:2152",
      },
      {
         type: "ADVISORY",
         url: "https://access.redhat.com/errata/RHSA-2018:2151",
      },
      {
         type: "ADVISORY",
         url: "https://access.redhat.com/errata/RHSA-2018:2150",
      },
      {
         type: "ADVISORY",
         url: "https://access.redhat.com/errata/RHSA-2018:2321",
      },
      {
         type: "WEB",
         url: "http://www.securitytracker.com/id/1041396",
      },
      {
         type: "ADVISORY",
         url: "https://access.redhat.com/errata/RHSA-2018:2585",
      },
      {
         type: "ADVISORY",
         url: "https://access.redhat.com/errata/RHBA-2018:3788",
      },
      {
         type: "ADVISORY",
         url: "https://access.redhat.com/errata/RHSA-2019:0054",
      },
      {
         type: "ADVISORY",
         url: "https://www.debian.org/security/2019/dsa-4396",
      },
      {
         type: "WEB",
         url: "http://lists.opensuse.org/opensuse-security-announce/2019-04/msg00021.html",
      },
      {
         type: "WEB",
         url: "https://usn.ubuntu.com/4072-1/",
      },
      {
         type: "WEB",
         url: "https://lists.debian.org/debian-lts-announce/2019/09/msg00016.html",
      },
   ],
}


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.