werkzeug@0.8.2 vulnerabilities
The comprehensive WSGI web application library.
-
latest version
3.1.3
-
latest non vulnerable version
-
first published
17 years ago
-
latest version published
16 days ago
-
licenses detected
- [0,)
Direct Vulnerabilities
Known vulnerabilities in the werkzeug package. This does not include vulnerabilities belonging to this package’s dependencies.
Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.Vulnerability | Vulnerable Version |
---|---|
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling in How to fix Allocation of Resources Without Limits or Throttling? Upgrade |
[,3.0.6)
|
Werkzeug is a WSGI web application library. Affected versions of this package are vulnerable to Directory Traversal due to a bypass for Note: This is only exploitable on Windows systems using Python versions prior to 3.11. How to fix Directory Traversal? Upgrade |
[,3.0.6)
|
Affected versions of this package are vulnerable to Remote Code Execution (RCE) due to insufficient hostname checks and the use of relative paths to resolve requests. When the debugger is enabled, an attacker can convince a user to enter their own PIN to interact with a domain and subdomain they control, and thereby cause malicious code to be executed. The demonstrated attack vector requires a number of conditions that render this attack very difficult to achieve, especially if the victim application is running in the recommended configuration of not having the debugger enabled in production. How to fix Remote Code Execution (RCE)? Upgrade |
[,3.0.3)
|
Affected versions of this package are vulnerable to Inefficient Algorithmic Complexity in multipart data parsing. An attacker can cause a denial of service and block worker processes from handling legitimate requests by sending crafted multipart data to an endpoint that will parse it, eventually exhausting or killing all available workers. Exploiting this vulnerability is possible if the uploaded file starts with How to fix Inefficient Algorithmic Complexity? Upgrade |
[,2.3.8)
[3.0.0,3.0.1)
|
Affected versions of this package are vulnerable to Denial of Service (DoS) when parsing multipart form data. An attacker can trigger the opening of multipart files containing a large number of file parts, which are processed using How to fix Denial of Service (DoS)? Upgrade |
[,2.2.3)
|
Affected versions of this package are vulnerable to Access Restriction Bypass that allows a malicious application on an adjacent subdomain to present "nameless" cookies that look like How to fix Access Restriction Bypass? Upgrade |
[,2.2.3)
|
Affected versions of this package are vulnerable to Directory Traversal in Note: This vulnerability is exploitable only in Windows environments. How to fix Directory Traversal? Upgrade |
[,0.15.5)
|
Werkzeug is a WSGI web application library. Affected versions of this package are vulnerable to Open Redirect. It is possible to redirect a user in How to fix Open Redirect? Upgrade |
[,0.11.6)
|
Werkzeug is a WSGI web application library. Affected versions of this package are vulnerable to Insufficient Randomness. How to fix Insufficient Randomness? Upgrade |
[,0.12)
|
Werkzeug is a WSGI web application library. Affected versions of this package are vulnerable to Insufficient Randomness when used with Docker, it has insufficient debugger PIN randomness because Docker containers share the same machine id. How to fix Insufficient Randomness? Upgrade |
[,0.15.3)
|
werkzeug is a comprehensive WSGI web application library. Affected versions of this package are vulnerable to Cross-site Scripting (XSS). It allows remote attackers to inject arbitrary web script or HTML via a field that contains an exception message. How to fix Cross-site Scripting (XSS)? Upgrade |
[,0.11.11)
|
Affected versions of this package are vulnerable to Cross-site Scripting (XSS) attacks via the |
[,0.11.11)
|
Affected versions of this package are vulnerable to Cross-site Scripting (XSS) attacks due to the lack of sanitization of the redirect url links. |
[,0.8.3)
|