Search for packages
| purl | pkg:deb/debian/python-werkzeug@0.9.6%2Bdfsg-1 |
| Next non-vulnerable version | 2.2.2-3+deb12u1 |
| Latest non-vulnerable version | 2.2.2-3+deb12u1 |
| Risk | 10.0 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-3t8t-yt9b-1fce
Aliases: CVE-2016-10516 GHSA-h2fp-xgx6-xh6f PYSEC-2017-43 |
Cross-site scripting (XSS) vulnerability in the render_full function in debug/tbtools.py in the debugger in Pallets Werkzeug before 0.11.11 (as used in Pallets Flask and other products) allows remote attackers to inject arbitrary web script or HTML via a field that contains an exception message. |
Affected by 4 other vulnerabilities. |
|
VCID-56e9-csba-kqa8
Aliases: CVE-2019-14806 GHSA-gq9m-qvpx-68hc PYSEC-2019-140 |
Pallets Werkzeug before 0.15.3, when used with Docker, has insufficient debugger PIN randomness because Docker containers share the same machine id. |
Affected by 1 other vulnerability. |
|
VCID-kycs-rbvn-z3e7
Aliases: CVE-2023-23934 GHSA-px8h-6qxv-m22q PYSEC-2023-57 |
Werkzeug is a comprehensive WSGI web application library. Browsers may allow "nameless" cookies that look like `=value` instead of `key=value`. A vulnerable browser may allow a compromised application on an adjacent subdomain to exploit this to set a cookie like `=__Host-test=bad` for another subdomain. Werkzeug prior to 2.2.3 will parse the cookie `=__Host-test=bad` as __Host-test=bad`. If a Werkzeug application is running next to a vulnerable or malicious subdomain which sets such a cookie using a vulnerable browser, the Werkzeug application will see the bad cookie value but the valid cookie key. The issue is fixed in Werkzeug 2.2.3. |
Affected by 1 other vulnerability. |
|
VCID-q13z-976n-gke3
Aliases: CVE-2020-28724 GHSA-3p3h-qghp-hvh2 PYSEC-2020-157 |
Open redirect vulnerability in werkzeug before 0.11.6 via a double slash in the URL. |
Affected by 4 other vulnerabilities. |
|
VCID-qjcy-54yn-qybs
Aliases: CVE-2024-34069 GHSA-2g68-c3qc-8985 |
Werkzeug debugger vulnerable to remote execution when interacting with attacker controlled domain The debugger in affected versions of Werkzeug can allow an attacker to execute code on a developer's machine under some circumstances. This requires the attacker to get the developer to interact with a domain and subdomain they control, and enter the debugger PIN, but if they are successful it allows access to the debugger even if it is only running on localhost. This also requires the attacker to guess a URL in the developer's application that will trigger the debugger. |
Affected by 0 other vulnerabilities. |
|
VCID-qn4r-71h3-sbgb
Aliases: CVE-2023-25577 GHSA-xg9f-g7g7-2323 PYSEC-2023-58 |
Werkzeug is a comprehensive WSGI web application library. Prior to version 2.2.3, Werkzeug's multipart form data parser will parse an unlimited number of parts, including file parts. Parts can be a small amount of bytes, but each requires CPU time to parse and may use more memory as Python data. If a request can be made to an endpoint that accesses `request.data`, `request.form`, `request.files`, or `request.get_data(parse_form_data=False)`, it can cause unexpectedly high resource usage. This allows an attacker to cause a denial of service by sending crafted multipart data to an endpoint that will parse it. The amount of CPU time required can block worker processes from handling legitimate requests. The amount of RAM required can trigger an out of memory kill of the process. Unlimited file parts can use up memory and file handles. If many concurrent requests are sent continuously, this can exhaust or kill all available workers. Version 2.2.3 contains a patch for this issue. |
Affected by 1 other vulnerability. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| This package is not known to fix vulnerabilities. | ||