ghsa-6jgw-rgmm-7cv6
Vulnerability from github
Published
2024-10-15 15:30
Modified
2024-10-15 17:04
Severity ?
5.3 (Medium) - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
4.8 (Medium) - CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N
Summary
PyO3 has a risk of use-after-free in `borrowed` reads from Python weak references
Details

The family of functions to read "borrowed" values from Python weak references were fundamentally unsound, because the weak reference does itself not have ownership of the value. At any point the last strong reference could be cleared and the borrowed value would become dangling.

In PyO3 0.22.4 these functions have all been deprecated and patched to leak a strong reference as a mitigation. PyO3 0.23 will remove these functions entirely.

Show details on source website

To clipboard 

{
   affected: [
      {
         package: {
            ecosystem: "crates.io",
            name: "pyo3",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "0.22.0",
                  },
                  {
                     fixed: "0.22.4",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
      },
   ],
   aliases: [
      "CVE-2024-9979",
   ],
   database_specific: {
      cwe_ids: [
         "CWE-416",
      ],
      github_reviewed: true,
      github_reviewed_at: "2024-10-15T17:04:56Z",
      nvd_published_at: "2024-10-15T14:15:05Z",
      severity: "MODERATE",
   },
   details: "The family of functions to read \"borrowed\" values from Python weak references were fundamentally unsound, because the weak reference does itself not have ownership of the value. At any point the last strong reference could be cleared and the borrowed value would become dangling.\n\nIn PyO3 0.22.4 these functions have all been deprecated and patched to leak a strong reference as a mitigation. PyO3 0.23 will remove these functions entirely.",
   id: "GHSA-6jgw-rgmm-7cv6",
   modified: "2024-10-15T17:04:56Z",
   published: "2024-10-15T15:30:56Z",
   references: [
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2024-9979",
      },
      {
         type: "WEB",
         url: "https://github.com/PyO3/pyo3/pull/4590",
      },
      {
         type: "WEB",
         url: "https://access.redhat.com/security/cve/CVE-2024-9979",
      },
      {
         type: "WEB",
         url: "https://bugzilla.redhat.com/show_bug.cgi?id=2318646",
      },
      {
         type: "WEB",
         url: "https://crates.io/crates/pyo3",
      },
      {
         type: "PACKAGE",
         url: "https://github.com/PyO3/pyo3",
      },
      {
         type: "WEB",
         url: "https://rustsec.org/advisories/RUSTSEC-2024-0378.html",
      },
   ],
   schema_version: "1.4.0",
   severity: [
      {
         score: "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L",
         type: "CVSS_V3",
      },
      {
         score: "CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N",
         type: "CVSS_V4",
      },
   ],
   summary: " PyO3 has a risk of use-after-free in `borrowed` reads from Python weak references",
}


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.