tarfile hardlink fallback ignores custom extraction filter rejection via None
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 3.10.22, 3.11.17, 3.12.15, 3.13.16, 3.14.9, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
When tarfile extracts a link on a system that doesn't support links, it falls back to extracting a member from the archive. In this case, the filter function is run twice: once for the extracted member, and once with name set to the location of the link. For one of the calls, the return value was ignored. Instead, the member should be skipped if either call returns None.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Python Software Foundation CPython
fixed in 3.10.22; From 3.11.0 · fixed in 3.11.17; From 3.12.0 · fixed in 3.12.15; From 3.13.0 · fixed in 3.13.16; From 3.14.0 · fixed in 3.14.9; From 3.15.0a1 · fixed in 3.15.0rc3
- libpythonBitnami
fixed in 3.10.22; From 3.11.0 · fixed in 3.11.17; From 3.12.0 · fixed in 3.12.15; From 3.13.0 · fixed in 3.13.16; From 3.14.0
- pythonBitnami
fixed in 3.10.22; From 3.11.0 · fixed in 3.11.17; From 3.12.0 · fixed in 3.12.15; From 3.13.0 · fixed in 3.13.16; From 3.14.0
- python-minBitnami
fixed in 3.10.22; From 3.11.0 · fixed in 3.11.17; From 3.12.0 · fixed in 3.12.15; From 3.13.0 · fixed in 3.13.16; From 3.14.0