GHSA-cm45-jwqh-659g json
Tar extraction fix bypass via symlink and parent traversal on fallback Python 3.10.0 - 3.10.12 and 3.11.0 - 3.11.4
published 18h ago modified 18h ago
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository python-poetry/poetry. GitHub has not reviewed it into the GitHub Advisory Database and no CVE record has reached us yet, so everything here comes from the maintainers alone. Read the full advisory on GitHub.
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
Security advisory published by the maintainers of python-poetry/poetry for poetry: the maintainers' own advisory, not a reviewed GitHub Advisory Database entry. The full advisory is on GitHub.
Patch / fix
- pypi poetry 2.4.2
Is GHSA-cm45-jwqh-659g in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | poetry | <=2.4.1 |
2.4.2 |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
Sources
- Maintainer advisory GHSA-cm45-jwqh-659g
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of python-poetry/poetry published their own advisory on GitHub. Its facts and headline are shown here; the description stays on GitHub.