Palletsprojects Werkzeug
By the Year
In 2024 there have been 0 vulnerabilities in Palletsprojects Werkzeug . Last year Werkzeug had 3 security vulnerabilities published. Right now, Werkzeug is on track to have less security vulnerabilities in 2024 than it did last year.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2024 | 0 | 0.00 |
| 2023 | 3 | 6.17 |
| 2022 | 1 | 9.80 |
| 2021 | 0 | 0.00 |
| 2020 | 1 | 6.10 |
| 2019 | 1 | 7.50 |
| 2018 | 0 | 0.00 |
It may take a day or so for new Werkzeug vulnerabilities to show up in the stats or in the list of recent security vulnerabilties. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Palletsprojects Werkzeug Security Vulnerabilities
Werkzeug is a comprehensive WSGI web application library
CVE-2023-46136
7.5 - High
- October 25, 2023
Werkzeug is a comprehensive WSGI web application library. If an upload of a file that starts with CR or LF and then is followed by megabytes of data without these characters: all of these bytes are appended chunk by chunk into internal bytearray and lookup for boundary is performed on growing buffer. 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. This vulnerability has been patched in version 3.0.1.
Memory Corruption
Werkzeug is a comprehensive WSGI web application library
CVE-2023-25577
7.5 - High
- February 14, 2023
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.
Allocation of Resources Without Limits or Throttling
Werkzeug is a comprehensive WSGI web application library
CVE-2023-23934
3.5 - Low
- February 14, 2023
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.
Improper Input Validation
Improper parsing of HTTP requests in Pallets Werkzeug v2.1.0 and below
CVE-2022-29361
9.8 - Critical
- May 25, 2022
Improper parsing of HTTP requests in Pallets Werkzeug v2.1.0 and below allows attackers to perform HTTP Request Smuggling using a crafted HTTP request with multiple requests included inside the body. NOTE: the vendor's position is that this behavior can only occur in unsupported configurations involving development mode and an HTTP server from outside the Werkzeug project
HTTP Request Smuggling
Open redirect vulnerability in werkzeug before 0.11.6
CVE-2020-28724
6.1 - Medium
- November 18, 2020
Open redirect vulnerability in werkzeug before 0.11.6 via a double slash in the URL.
Open Redirect
Pallets Werkzeug before 0.15.3, when used with Docker, has insufficient debugger PIN randomness
CVE-2019-14806
7.5 - High
- August 09, 2019
Pallets Werkzeug before 0.15.3, when used with Docker, has insufficient debugger PIN randomness because Docker containers share the same machine id.
Insufficient Entropy
Stay on top of Security Vulnerabilities
Want an email whenever new vulnerabilities are published for OpenSuse Leap or by Palletsprojects? Click the Watch button to subscribe.
