GHSA-vxcf-c7mx-pg53: Pyo3 Build Corruption When Using `PYO3_CONFIG_FILE` Vulnerability

MODERATE
Share
Published
Advisory Summary

GHSA-vxcf-c7mx-pg53 is a MODERATE build corruption when using `pyo3_config_file` vulnerability (General Security Weakness) affecting Pyo3 libraries in the crates.io ecosystem. The issue involves build corruption when using `pyo3_config_file` environment variable. Remediation is available by upgrading affected packages to version 0.23.3.

GHSA-vxcf-c7mx-pg53 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-vxcf-c7mx-pg53
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Pyo3
Package Ecosystem crates.io
Published Date
Last Updated

How to Fix GHSA-vxcf-c7mx-pg53

To remediate this vulnerability, upgrade all affected Pyo3 dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

pyo3 fixed: 0.23.3 
Upgrade pyo3 to 0.23.3
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

inspect dependencies for pyo3

How to Check if You Are Affected

To determine whether your application is affected by GHSA-vxcf-c7mx-pg53, inspect your project dependencies for Pyo3:

inspect dependencies for pyo3

Analyze the terminal output to locate any version of Pyo3 in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.23.3), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Pyo3, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

In PyO3 0.23.0 the `PYO3_CONFIG_FILE` environment variable used to configure builds regressed such that changing the environment variable would no longer trigger PyO3 to reconfigure and recompile. In combination with workflows using tools such as `maturin` to build for multiple versions in a single build, this leads to Python wheels being compiled against the wrong Python API version. All users who distribute artefacts for multiple Python versions are encouraged to update and rebuild with PyO3 0.23.3. Affected wheels produced from PyO3 0.23.0 through 0.23.2 are highly unstable and will crash the Python interpreter in unpredictable ways.

GHSA-vxcf-c7mx-pg53 Affected Pyo3 Versions

1 component(s)
Fixed Versions:
0.23.3
Product / Package Ecosystem Affected Versions Fixed Version
pyo3
 crates.io
≥ 0.23.0
< 0.23.3
0.23.3

References

Pyo3 Source Repository REPOSITORY
https://github.com/PyO3/pyo3/issues/4757
Pyo3 Source Repository REPOSITORY
https://github.com/PyO3/pyo3
rustsec.org/advisories/rustsec-... WEB
https://rustsec.org/advisories/RUSTSEC-2024-0409.html

Frequently Asked Questions

What is GHSA-vxcf-c7mx-pg53?
GHSA-vxcf-c7mx-pg53 is a security vulnerability in Pyo3 involving Build corruption when using `PYO3_CONFIG_FILE` environment variable under General Security Weakness.
Which Pyo3 versions are affected?
Affected versions include releases prior to 0.23.3 across affected packages: pyo3.
What version fixes GHSA-vxcf-c7mx-pg53?
Upgrading to 0.23.3 (or the latest patched release for your respective branch) resolves the vulnerability.
Is pyo3 affected?
Yes, pyo3 is affected in releases prior to 0.23.3. Upgrade your dependency to 0.23.3 or later.
What CWE is associated with GHSA-vxcf-c7mx-pg53?
GHSA-vxcf-c7mx-pg53 is classified under General Security Weakness.
How can I check crates.io dependencies for GHSA-vxcf-c7mx-pg53?
Run the dependency tree command: 'inspect dependencies for pyo3'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-vxcf-c7mx-pg53",
  "modified" : "2024-12-05T19:06:20Z",
  "published" : "2024-12-05T19:06:20Z",
  "aliases" : [ ],
  "summary" : "Build corruption when using `PYO3_CONFIG_FILE` environment variable",
  "details" : "In PyO3 0.23.0 the `PYO3_CONFIG_FILE` environment variable used to configure builds regressed such that changing the environment variable would no longer trigger PyO3 to reconfigure and recompile. In combination with workflows using tools such as `maturin` to build for multiple versions in a single build, this leads to Python wheels being compiled against the wrong Python API version.\n\nAll users who distribute artefacts for multiple Python versions are encouraged to update and rebuild with PyO3 0.23.3. Affected wheels produced from PyO3 0.23.0 through 0.23.2 are highly unstable and will crash the Python interpreter in unpredictable ways.\n",
  "severity" : [ ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "pyo3"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.23.0"
      }, {
        "fixed" : "0.23.3"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/PyO3/pyo3/issues/4757"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/PyO3/pyo3"
  }, {
    "type" : "WEB",
    "url" : "https://rustsec.org/advisories/RUSTSEC-2024-0409.html"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-12-05T19:06:20Z",
    "nvd_published_at" : null
  }
}