Palletsprojects
Products by Palletsprojects Sorted by Most Security Vulnerabilities since 2018
By the Year
In 2024 there have been 1 vulnerability in Palletsprojects with an average score of 6.1 out of ten. Last year Palletsprojects had 4 security vulnerabilities published. Right now, Palletsprojects is on track to have less security vulnerabilities in 2024 than it did last year. Last year, the average CVE base score was greater by 0.40
Year | Vulnerabilities | Average Score |
---|---|---|
2024 | 1 | 6.10 |
2023 | 4 | 6.50 |
2022 | 1 | 9.80 |
2021 | 1 | 5.30 |
2020 | 1 | 6.10 |
2019 | 3 | 7.87 |
2018 | 1 | 7.50 |
It may take a day or so for new Palletsprojects 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 Security Vulnerabilities
Jinja is an extensible templating engine
CVE-2024-22195
6.1 - Medium
- January 11, 2024
Jinja is an extensible templating engine. Special placeholders in the template allow writing code similar to Python syntax. It is possible to inject arbitrary HTML attributes into the rendered HTML template, potentially leading to Cross-Site Scripting (XSS). The Jinja `xmlattr` filter can be abused to inject arbitrary HTML attribute keys and values, bypassing the auto escaping mechanism and potentially leading to XSS. It may also be possible to bypass attribute validation checks if they are blacklist-based.
XSS
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
Flask is a lightweight WSGI web application framework
CVE-2023-30861
7.5 - High
- May 02, 2023
Flask is a lightweight WSGI web application framework. When all of the following conditions are met, a response containing data intended for one client may be cached and subsequently sent by the proxy to other clients. If the proxy also caches `Set-Cookie` headers, it may send one client's `session` cookie to other clients. The severity depends on the application's use of the session and the proxy's behavior regarding cookies. The risk depends on all these conditions being met. 1. The application must be hosted behind a caching proxy that does not strip cookies or ignore responses with cookies. 2. The application sets `session.permanent = True` 3. The application does not access or modify the session at any point during a request. 4. `SESSION_REFRESH_EACH_REQUEST` enabled (the default). 5. The application does not set a `Cache-Control` header to indicate that a page is private or should not be cached. This happens because vulnerable versions of Flask only set the `Vary: Cookie` header when the session is accessed or modified, not when it is refreshed (re-sent to update the expiration) without being accessed or modified. This issue has been fixed in versions 2.3.2 and 2.2.5.
Use of Persistent Cookies Containing Sensitive Information
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
This affects the package jinja2 from 0.0.0 and before 2.11.3
CVE-2020-28493
5.3 - Medium
- February 01, 2021
This affects the package jinja2 from 0.0.0 and before 2.11.3. The ReDoS vulnerability is mainly due to the `_punctuation_re regex` operator and its use of multiple wildcards. The last wildcard is the most exploitable as it searches for trailing punctuation. This issue can be mitigated by Markdown to format user content instead of the urlize filter, or by implementing request timeouts and limiting process memory.
Resource Exhaustion
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
The Pallets Project Flask before 1.0 is affected by: unexpected memory usage
CVE-2019-1010083
7.5 - High
- July 17, 2019
The Pallets Project Flask before 1.0 is affected by: unexpected memory usage. The impact is: denial of service. The attack vector is: crafted encoded JSON data. The fixed version is: 1. NOTE: this may overlap CVE-2018-1000656.
In Pallets Jinja before 2.10.1, str.format_map
CVE-2019-10906
8.6 - High
- April 07, 2019
In Pallets Jinja before 2.10.1, str.format_map allows a sandbox escape.
The Pallets Project flask version Before 0.12.3 contains a CWE-20: Improper Input Validation vulnerability in flask
CVE-2018-1000656
7.5 - High
- August 20, 2018
The Pallets Project flask version Before 0.12.3 contains a CWE-20: Improper Input Validation vulnerability in flask that can result in Large amount of memory usage possibly leading to denial of service. This attack appear to be exploitable via Attacker provides JSON data in incorrect encoding. This vulnerability appears to have been fixed in 0.12.3. NOTE: this may overlap CVE-2019-1010083.
Improper Input Validation