Show filters
304 Total Results
Displaying 51-60 of 304
Sort by:
Attacker Value
Unknown
CVE-2023-24329
Disclosure Date: February 17, 2023 (last updated October 08, 2023)
An issue in the urllib.parse component of Python before 3.11.4 allows attackers to bypass blocklisting methods by supplying a URL that starts with blank characters.
0
Attacker Value
Unknown
CVE-2023-24816
Disclosure Date: February 10, 2023 (last updated October 08, 2023)
IPython (Interactive Python) is a command shell for interactive computing in multiple programming languages, originally developed for the Python programming language. Versions prior to 8.1.0 are subject to a command injection vulnerability with very specific prerequisites. This vulnerability requires that the function `IPython.utils.terminal.set_term_title` be called on Windows in a Python environment where ctypes is not available. The dependency on `ctypes` in `IPython.utils._process_win32` prevents the vulnerable code from ever being reached in the ipython binary. However, as a library that could be used by another tool `set_term_title` could be called and hence introduce a vulnerability. Should an attacker get untrusted input to an instance of this function they would be able to inject shell commands as current process and limited to the scope of the current process. Users of ipython as a library are advised to upgrade. Users unable to upgrade should ensure that any calls to the `I…
0
Attacker Value
Unknown
CVE-2022-40899
Disclosure Date: December 23, 2022 (last updated October 08, 2023)
An issue discovered in Python Charmers Future 0.18.2 and earlier allows remote attackers to cause a denial of service via crafted Set-Cookie header from malicious web server.
0
Attacker Value
Unknown
CVE-2022-40897
Disclosure Date: December 23, 2022 (last updated October 08, 2023)
Python Packaging Authority (PyPA) setuptools before 65.5.1 allows remote attackers to cause a denial of service via HTML in a crafted package or custom PackageIndex page. There is a Regular Expression Denial of Service (ReDoS) in package_index.py.
0
Attacker Value
Unknown
CVE-2022-46609
Disclosure Date: December 14, 2022 (last updated October 08, 2023)
Python3-RESTfulAPI commit d9907f14e9e25dcdb54f5b22252b0e9452e3970e and e772e0beee284c50946e94c54a1d43071ca78b74 was discovered to contain a code execution backdoor via the request package. This vulnerability allows attackers to access sensitive user information and digital currency keys, as well as escalate privileges.
0
Attacker Value
Unknown
CVE-2022-24439
Disclosure Date: December 06, 2022 (last updated January 09, 2024)
All versions of package gitpython are vulnerable to Remote Code Execution (RCE) due to improper user input validation, which makes it possible to inject a maliciously crafted remote URL into the clone command. Exploiting this vulnerability is possible because the library makes external calls to git without sufficient sanitization of input arguments.
0
Attacker Value
Unknown
CVE-2022-45198
Disclosure Date: November 14, 2022 (last updated December 22, 2024)
Pillow before 9.2.0 performs Improper Handling of Highly Compressed GIF Data (Data Amplification).
0
Attacker Value
Unknown
CVE-2022-45199
Disclosure Date: November 14, 2022 (last updated December 22, 2024)
Pillow before 9.3.0 allows denial of service via SAMPLESPERPIXEL.
0
Attacker Value
Unknown
CVE-2022-42966
Disclosure Date: November 09, 2022 (last updated December 22, 2024)
An exponential ReDoS (Regular Expression Denial of Service) can be triggered in the cleo PyPI package, when an attacker is able to supply arbitrary input to the Table.set_rows method
0
Attacker Value
Unknown
CVE-2022-45061
Disclosure Date: November 09, 2022 (last updated November 08, 2023)
An issue was discovered in Python before 3.11.1. An unnecessary quadratic algorithm exists in one path when processing some inputs to the IDNA (RFC 3490) decoder, such that a crafted, unreasonably long name being presented to the decoder could lead to a CPU denial of service. Hostnames are often supplied by remote servers that could be controlled by a malicious actor; in such a scenario, they could trigger excessive CPU consumption on the client attempting to make use of an attacker-supplied supposed hostname. For example, the attack payload could be placed in the Location header of an HTTP response with status code 302. A fix is planned in 3.11.1, 3.10.9, 3.9.16, 3.8.16, and 3.7.16.
0