pysec-2020-216
Vulnerability from pysec
Published
2020-06-26 20:15
Modified
2021-07-25 23:34
Details

The Beaker library through 1.11.0 for Python is affected by deserialization of untrusted data, which could lead to arbitrary code execution.




{
   affected: [
      {
         package: {
            ecosystem: "PyPI",
            name: "beaker",
            purl: "pkg:pypi/beaker",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "0",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
         versions: [
            "0.5",
            "0.6",
            "0.6.1",
            "0.6.2",
            "0.6.3",
            "0.7",
            "0.7.1",
            "0.7.2",
            "0.7.3",
            "0.7.4",
            "0.7.5",
            "0.8",
            "0.8.1",
            "0.9",
            "0.9.1",
            "0.9.2",
            "0.9.3",
            "0.9.4",
            "0.9.5",
            "1.0",
            "1.0.1",
            "1.0.2",
            "1.0.3",
            "1.1",
            "1.1.1",
            "1.1.2",
            "1.1.3",
            "1.10.0",
            "1.10.1",
            "1.11.0",
            "1.2",
            "1.2.1",
            "1.2.2",
            "1.2.3",
            "1.3",
            "1.3.1",
            "1.3.1dev",
            "1.4",
            "1.4.1",
            "1.4.2",
            "1.4.3",
            "1.5",
            "1.5.1",
            "1.5.2",
            "1.5.3",
            "1.5.4",
            "1.6",
            "1.6.1",
            "1.6.2",
            "1.6.3",
            "1.6.4",
            "1.6.5",
            "1.6.5.post1",
            "1.7.0",
            "1.7.0dev",
            "1.8.0",
            "1.8.1",
            "1.9.0",
            "1.9.1",
         ],
      },
   ],
   aliases: [
      "CVE-2013-7489",
      "GHSA-3cwm-7jmm-774w",
   ],
   details: "The Beaker library through 1.11.0 for Python is affected by deserialization of untrusted data, which could lead to arbitrary code execution.",
   id: "PYSEC-2020-216",
   modified: "2021-07-25T23:34:27.636176Z",
   published: "2020-06-26T20:15:00Z",
   references: [
      {
         type: "REPORT",
         url: "https://github.com/bbangert/beaker/issues/191",
      },
      {
         type: "REPORT",
         url: "https://bugzilla.redhat.com/show_bug.cgi?id=1850105",
      },
      {
         type: "WEB",
         url: "https://www.openwall.com/lists/oss-security/2020/05/14/11",
      },
      {
         type: "ADVISORY",
         url: "https://github.com/advisories/GHSA-3cwm-7jmm-774w",
      },
   ],
}


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.