pysec-2018-49
Vulnerability from pysec
Published
2018-06-27 12:29
Modified
2021-07-05 00:01
Details

In PyYAML before 5.1, the yaml.load() API could execute arbitrary code if used with untrusted data. The load() function has been deprecated in version 5.1 and the 'UnsafeLoader' has been introduced for backward compatibility with the function.

Impacted products
Name purl
pyyaml pkg:pypi/pyyaml
Aliases


To clipboard 

{
   affected: [
      {
         package: {
            ecosystem: "PyPI",
            name: "pyyaml",
            purl: "pkg:pypi/pyyaml",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "0",
                  },
                  {
                     fixed: "5.1",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
         versions: [
            "3.01",
            "3.02",
            "3.03",
            "3.04",
            "3.05",
            "3.06",
            "3.07",
            "3.08",
            "3.09",
            "3.10",
            "3.11",
            "3.12",
            "3.13",
            "3.13b1",
            "3.13rc1",
            "4.2b1",
            "4.2b2",
            "4.2b4",
            "5.1b1",
            "5.1b3",
            "5.1b5",
            "5.1b7",
         ],
      },
   ],
   aliases: [
      "CVE-2017-18342",
      "GHSA-rprw-h62v-c2w7",
   ],
   details: "In PyYAML before 5.1, the yaml.load() API could execute arbitrary code if used with untrusted data. The load() function has been deprecated in version 5.1 and the 'UnsafeLoader' has been introduced for backward compatibility with the function.",
   id: "PYSEC-2018-49",
   modified: "2021-07-05T00:01:25.530537Z",
   published: "2018-06-27T12:29:00Z",
   references: [
      {
         type: "WEB",
         url: "https://github.com/yaml/pyyaml/pull/74",
      },
      {
         type: "WEB",
         url: "https://github.com/yaml/pyyaml/blob/master/CHANGES",
      },
      {
         type: "WEB",
         url: "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/M6JCFGEIEOFMWWIXGHSELMKQDD4CV2BA/",
      },
      {
         type: "WEB",
         url: "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/KSQQMRUQSXBSUXLCRD3TSZYQ7SEZRKCE/",
      },
      {
         type: "WEB",
         url: "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/JEX7IPV5P2QJITAMA5Z63GQCZA5I6NVZ/",
      },
      {
         type: "WEB",
         url: "https://github.com/yaml/pyyaml/wiki/PyYAML-yaml.load(input)-Deprecation",
      },
      {
         type: "REPORT",
         url: "https://github.com/marshmallow-code/apispec/issues/278",
      },
      {
         type: "REPORT",
         url: "https://github.com/yaml/pyyaml/issues/193",
      },
      {
         type: "ADVISORY",
         url: "https://security.gentoo.org/glsa/202003-45",
      },
      {
         type: "ADVISORY",
         url: "https://github.com/advisories/GHSA-rprw-h62v-c2w7",
      },
   ],
}


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.