CVE-2023-45805

unknown
Published 2023-10-20 ยท Modified 2024-02-16
CVSS v3
โ€”
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
CVSS v4 NEW
โ€”
not yet in upstream
VIR risk
โ€”

Description

pdm is a Python package and dependency manager supporting the latest PEP standards. It's possible to craft a malicious `pdm.lock` file that could allow e.g. an insider or a malicious open source project to appear to depend on a trusted PyPI project, but actually install another project. A project `foo` can be targeted by creating the project `foo-2` and uploading the file `foo-2-2.tar.gz` to pypi.org. PyPI will see this as project `foo-2` version `2`, while PDM will see this as project `foo` version `2-2`. The version must only be `parseable as a version` and the filename must be a prefix of the project name, but it's not verified to match the version being installed. Version `2-2` is also not a valid normalized version per PEP 440. Matching the project name exactly (not just prefix) would fix the issue. When installing dependencies with PDM, what's actually installed could differ from what's listed in `pyproject.toml` (including arbitrary code execution on install). It could also be used for downgrade attacks by only changing the version. This issue has been addressed in commit `6853e2642df` which is included in release version `2.9.4`. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Predictions

Exploit likelihood
20%
Patch ETA
โ€”

Heuristic predictions, AS-IS, for prioritization only.

Mitigations

Mitigation details

Source: Debian Security Tracker ยท View original โ†— ยท DFSG

CVE-2023-45805 NameCVE-2023-45805 Descriptionpdm is a Python package and dependency manager supporting the latest PEP standards. It's possible to craft a malicious `pdm.lock` file that could allow e.g. an insider or a malicious open source project to appear to depend on a trusted PyPI project, but actually install another project. A project `foo` can be targeted by creating the project `foo-2`โ€ฆ

Workaround

s for this vulnerability. SourceCVE (at NVD; CERT, ENISA, LWN, oss-sec, fulldisc, Debian ELTS, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more) Debian Bugs1054428 Vulnerable and fixed packages The table below lists information on source packages. Source PackageReleaseVersionStatus pdm (PTS)bookworm2.2.1+ds1-1vulnerable trixie2.20.1+ds1-2fixed forky, sid2.27.0-1fixed The information below is based on the following data on fixed versions. PackageTypeReleaseFixed VersionUrgencyOriginDebian Bugs pdmsource(unstable)2.20.0.post1+ds1-11054428 Notes [bookworm] - pdm <no-dsa> (Minor issue) https://github.com/pdm-project/pdm/security/advisories/GHSA-j44v-mmf2-xvm9 https://github.com/pdm-project/pdm/commit/6853e2642dfa281d4a9958fbc6c95b7e32d84831 (2.10.0)

CVE-2023-45805

NameCVE-2023-45805
Descriptionpdm is a Python package and dependency manager supporting the latest PEP standards. It's possible to craft a malicious `pdm.lock` file that could allow e.g. an insider or a malicious open source project to appear to depend on a trusted PyPI project, but actually install another project. A project `foo` can be targeted by creating the project `foo-2` and uploading the file `foo-2-2.tar.gz` to pypi.org. PyPI will see this as project `foo-2` version `2`, while PDM will see this as project `foo` version `2-2`. The version must only be `parseable as a version` and the filename must be a prefix of the project name, but it's not verified to match the version being installed. Version `2-2` is also not a valid normalized version per PEP 440. Matching the project name exactly (not just prefix) would fix the issue. When installing dependencies with PDM, what's actually installed could differ from what's listed in `pyproject.toml` (including arbitrary code execution on install). It could also be used for downgrade attacks by only changing the version. This issue has been addressed in commit `6853e2642df` which is included in release version `2.9.4`. Users are advised to upgrade. There are no known workarounds for this vulnerability.
SourceCVE (at NVD; CERT, ENISA, LWN, oss-sec, fulldisc, Debian ELTS, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more)
Debian Bugs1054428

Vulnerable and fixed packages

The table below lists information on source packages.

Source PackageReleaseVersionStatus
pdm (PTS)bookworm2.2.1+ds1-1vulnerable
trixie2.20.1+ds1-2fixed
forky, sid2.27.0-1fixed

The information below is based on the following data on fixed versions.

PackageTypeReleaseFixed VersionUrgencyOriginDebian Bugs
pdmsource(unstable)2.20.0.post1+ds1-11054428

Notes

[bookworm] - pdm <no-dsa> (Minor issue)
https://github.com/pdm-project/pdm/security/advisories/GHSA-j44v-mmf2-xvm9
https://github.com/pdm-project/pdm/commit/6853e2642dfa281d4a9958fbc6c95b7e32d84831 (2.10.0)

Home - Debian Security - Source (Git)

Apply commands

text fix
Notes
[bookworm] - pdm <no-dsa> (Minor issue)https://github.com/pdm-project/pdm/security/advisories/GHSA-j44v-mmf2-xvm9https://github.com/pdm-project/pdm/commit/6853e2642dfa281d4a9958fbc6c95b7e32d84831 (2.10.0)

OS impact

debian Debian Mixed 4 releases
VersionStatusFixed in
trixie Fixed 2.20.0.post1+ds1-1
sid Fixed 2.20.0.post1+ds1-1
forky Fixed 2.20.0.post1+ds1-1
bookworm Affected โ€”

Package impact

EcosystemPackageVulnerableFixed
python PyPIpdm<=2.9.3

References

Community-verified mitigations for this CVE will appear above when contributors publish them.

Verify integrity in audit chain (admin only). AS-IS.