rpm package
suse/python313&distro=SUSE Linux Enterprise Module for Python 3 15 SP7
pkg:rpm/suse/python313&distro=SUSE%20Linux%20Enterprise%20Module%20for%20Python%203%2015%20SP7
Vulnerabilities (33)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2025-8291 | Med | 4.3 | < 3.13.9-150700.4.26.1 | 3.13.9-150700.4.26.1 | Oct 7, 2025 | The 'zipfile' module would not check the validity of the ZIP64 End of Central Directory (EOCD) Locator record offset value would not be used to locate the ZIP64 EOCD record, instead the ZIP64 EOCD record would be assumed to be the previous record in the ZIP archive. This could be | |
| CVE-2025-8194 | Hig | 7.5 | < 3.13.5-150700.4.20.1 | 3.13.5-150700.4.20.1 | Jul 28, 2025 | There is a defect in the CPython “tarfile” module affecting the “TarFile” extraction and entry enumeration APIs. The tar implementation would process tar archives with negative offsets without error, resulting in an infinite loop and deadlock during the parsing of maliciously cra | |
| CVE-2025-6069 | Med | 4.3 | < 3.13.5-150700.4.20.1 | 3.13.5-150700.4.20.1 | Jun 17, 2025 | The html.parser.HTMLParser class had worse-case quadratic complexity when processing certain crafted malformed inputs potentially leading to amplified denial-of-service. | |
| CVE-2025-4517 | Cri | 9.4 | < 3.13.5-150700.4.11.1 | 3.13.5-150700.4.11.1 | Jun 3, 2025 | Allows arbitrary filesystem writes outside the extraction directory during extraction with filter="data". You are affected by this vulnerability if using the tarfile module to extract untrusted tar archives using TarFile.extractall() or TarFile.extract() using the filter= param | |
| CVE-2025-4435 | Hig | 7.5 | < 3.13.5-150700.4.20.1 | 3.13.5-150700.4.20.1 | Jun 3, 2025 | When using a TarFile.errorlevel = 0 and extracting with a filter the documented behavior is that any filtered members would be skipped and not extracted. However the actual behavior of TarFile.errorlevel = 0 in affected versions is that the member would still be extracted and not | |
| CVE-2025-4330 | Hig | 7.5 | < 3.13.5-150700.4.11.1 | 3.13.5-150700.4.11.1 | Jun 3, 2025 | Allows the extraction filter to be ignored, allowing symlink targets to point outside the destination directory, and the modification of some file metadata. You are affected by this vulnerability if using the tarfile module to extract untrusted tar archives using TarFile.extrac | |
| CVE-2025-4138 | Hig | 7.5 | < 3.13.5-150700.4.11.1 | 3.13.5-150700.4.11.1 | Jun 3, 2025 | Allows the extraction filter to be ignored, allowing symlink targets to point outside the destination directory, and the modification of some file metadata. You are affected by this vulnerability if using the tarfile module to extract untrusted tar archives using TarFile.extrac | |
| CVE-2024-12718 | Med | 5.3 | < 3.13.5-150700.4.11.1 | 3.13.5-150700.4.11.1 | Jun 3, 2025 | Allows modifying some file metadata (e.g. last modified) with filter="data" or file permissions (chmod) with filter="tar" of files outside the extraction directory. You are affected by this vulnerability if using the tarfile module to extract untrusted tar archives using TarFile. | |
| CVE-2025-4516 | Med | — | < 3.13.5-150700.4.11.1 | 3.13.5-150700.4.11.1 | May 15, 2025 | There is an issue in CPython when using `bytes.decode("unicode_escape", error="ignore|replace")`. If you are not using the "unicode_escape" encoding or an error handler your usage is not affected. To work-around this issue you may stop using the error= handler and instead wrap th | |
| CVE-2025-1795 | Low | — | < 3.13.5-150700.4.11.1 | 3.13.5-150700.4.11.1 | Feb 28, 2025 | During an address list folding when a separating comma ends up on a folded line and that line is to be unicode-encoded then the separator itself is also unicode-encoded. Expected behavior is that the separating comma remains a plan comma. This can result in the address header bei | |
| CVE-2025-0938 | Med | — | < 3.13.5-150700.4.11.1 | 3.13.5-150700.4.11.1 | Jan 31, 2025 | The Python standard library functions `urllib.parse.urlsplit` and `urlparse` accepted domain names that included square brackets which isn't valid according to RFC 3986. Square brackets are only meant to be used as delimiters for specifying IPv6 and IPvFuture hosts in URLs. This | |
| CVE-2024-12254 | Hig | 7.5 | < 3.13.5-150700.4.11.1 | 3.13.5-150700.4.11.1 | Dec 6, 2024 | Starting in Python 3.12.0, the asyncio._SelectorSocketTransport.writelines() method would not "pause" writing and signal to the Protocol to drain the buffer to the wire once the write buffer reached the "high-water mark". Because of this, Protocols would not periodically drain | |
| CVE-2024-9287 | — | < 3.13.5-150700.4.11.1 | 3.13.5-150700.4.11.1 | Oct 22, 2024 | A vulnerability has been found in the CPython `venv` module and CLI where path names provided when creating a virtual environment were not quoted properly, allowing the creator to inject commands into virtual environment "activation" scripts (ie "source venv/bin/activate"). This |
- affected < 3.13.9-150700.4.26.1fixed 3.13.9-150700.4.26.1
The 'zipfile' module would not check the validity of the ZIP64 End of Central Directory (EOCD) Locator record offset value would not be used to locate the ZIP64 EOCD record, instead the ZIP64 EOCD record would be assumed to be the previous record in the ZIP archive. This could be
- affected < 3.13.5-150700.4.20.1fixed 3.13.5-150700.4.20.1
There is a defect in the CPython “tarfile” module affecting the “TarFile” extraction and entry enumeration APIs. The tar implementation would process tar archives with negative offsets without error, resulting in an infinite loop and deadlock during the parsing of maliciously cra
- affected < 3.13.5-150700.4.20.1fixed 3.13.5-150700.4.20.1
The html.parser.HTMLParser class had worse-case quadratic complexity when processing certain crafted malformed inputs potentially leading to amplified denial-of-service.
- affected < 3.13.5-150700.4.11.1fixed 3.13.5-150700.4.11.1
Allows arbitrary filesystem writes outside the extraction directory during extraction with filter="data". You are affected by this vulnerability if using the tarfile module to extract untrusted tar archives using TarFile.extractall() or TarFile.extract() using the filter= param
- affected < 3.13.5-150700.4.20.1fixed 3.13.5-150700.4.20.1
When using a TarFile.errorlevel = 0 and extracting with a filter the documented behavior is that any filtered members would be skipped and not extracted. However the actual behavior of TarFile.errorlevel = 0 in affected versions is that the member would still be extracted and not
- affected < 3.13.5-150700.4.11.1fixed 3.13.5-150700.4.11.1
Allows the extraction filter to be ignored, allowing symlink targets to point outside the destination directory, and the modification of some file metadata. You are affected by this vulnerability if using the tarfile module to extract untrusted tar archives using TarFile.extrac
- affected < 3.13.5-150700.4.11.1fixed 3.13.5-150700.4.11.1
Allows the extraction filter to be ignored, allowing symlink targets to point outside the destination directory, and the modification of some file metadata. You are affected by this vulnerability if using the tarfile module to extract untrusted tar archives using TarFile.extrac
- affected < 3.13.5-150700.4.11.1fixed 3.13.5-150700.4.11.1
Allows modifying some file metadata (e.g. last modified) with filter="data" or file permissions (chmod) with filter="tar" of files outside the extraction directory. You are affected by this vulnerability if using the tarfile module to extract untrusted tar archives using TarFile.
- affected < 3.13.5-150700.4.11.1fixed 3.13.5-150700.4.11.1
There is an issue in CPython when using `bytes.decode("unicode_escape", error="ignore|replace")`. If you are not using the "unicode_escape" encoding or an error handler your usage is not affected. To work-around this issue you may stop using the error= handler and instead wrap th
- affected < 3.13.5-150700.4.11.1fixed 3.13.5-150700.4.11.1
During an address list folding when a separating comma ends up on a folded line and that line is to be unicode-encoded then the separator itself is also unicode-encoded. Expected behavior is that the separating comma remains a plan comma. This can result in the address header bei
- affected < 3.13.5-150700.4.11.1fixed 3.13.5-150700.4.11.1
The Python standard library functions `urllib.parse.urlsplit` and `urlparse` accepted domain names that included square brackets which isn't valid according to RFC 3986. Square brackets are only meant to be used as delimiters for specifying IPv6 and IPvFuture hosts in URLs. This
- affected < 3.13.5-150700.4.11.1fixed 3.13.5-150700.4.11.1
Starting in Python 3.12.0, the asyncio._SelectorSocketTransport.writelines() method would not "pause" writing and signal to the Protocol to drain the buffer to the wire once the write buffer reached the "high-water mark". Because of this, Protocols would not periodically drain
- CVE-2024-9287Oct 22, 2024affected < 3.13.5-150700.4.11.1fixed 3.13.5-150700.4.11.1
A vulnerability has been found in the CPython `venv` module and CLI where path names provided when creating a virtual environment were not quoted properly, allowing the creator to inject commands into virtual environment "activation" scripts (ie "source venv/bin/activate"). This
Page 2 of 2