Patrowl/PatrowlEngines:engines/owl_code/requirements.txt
Find, fix and prevent vulnerabilities in your code.
high severity
- Vulnerable module: flask
- Introduced through: flask@2.0.1
Detailed paths
-
Introduced through: Patrowl/PatrowlEngines@Patrowl/PatrowlEngines#ff378eaef199de1945d5ca0f2da9348f24da956f › flask@2.0.1Remediation: Upgrade to flask@2.2.5.
Overview
Affected versions of this package are vulnerable to Information Exposure in the form of exposing the permanent session cookie, when all of the following conditions are met:
The application is hosted behind a caching proxy that does not strip cookies or ignore responses with cookies.
The application sets
session.permanent = True
.The application does not access or modify the session at any point during a request.
SESSION_REFRESH_EACH_REQUEST
is enabled (the default).The application does not set a
Cache-Control
header to indicate that a page is private or should not be cached.
A response containing data intended for one client may be cached and sent to other clients. If the proxy also caches Set-Cookie
headers, it may send one client's session
cookie to other clients. Under these conditions, the Vary: Cookie
header is not set when a session is refreshed (re-sent to update the expiration) without being accessed or modified.
Remediation
Upgrade flask
to version 2.2.5, 2.3.2 or higher.
References
high severity
- Vulnerable module: setuptools
- Introduced through: setuptools@65.5.1
Detailed paths
-
Introduced through: Patrowl/PatrowlEngines@Patrowl/PatrowlEngines#ff378eaef199de1945d5ca0f2da9348f24da956f › setuptools@65.5.1Remediation: Upgrade to setuptools@70.0.0.
Overview
Affected versions of this package are vulnerable to Improper Control of Generation of Code ('Code Injection') through the package_index
module's download functions due to the unsafe usage of os.system
. An attacker can execute arbitrary commands on the system by providing malicious URLs or manipulating the URLs retrieved from package index servers.
Note
Because easy_install
and package_index
are deprecated, the exploitation surface is reduced, but it's conceivable through social engineering or minor compromise to a package index could grant remote access.
Remediation
Upgrade setuptools
to version 70.0.0 or higher.
References
high severity
- Vulnerable module: werkzeug
- Introduced through: werkzeug@2.2.3 and flask@2.0.1
Detailed paths
-
Introduced through: Patrowl/PatrowlEngines@Patrowl/PatrowlEngines#ff378eaef199de1945d5ca0f2da9348f24da956f › werkzeug@2.2.3Remediation: Upgrade to werkzeug@3.0.3.
-
Introduced through: Patrowl/PatrowlEngines@Patrowl/PatrowlEngines#ff378eaef199de1945d5ca0f2da9348f24da956f › flask@2.0.1 › werkzeug@2.2.3Remediation: Upgrade to flask@2.0.1.
Overview
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.
Remediation
Upgrade werkzeug
to version 3.0.3 or higher.
References
high severity
new
- Module: patrowlenginesutils
- Introduced through: patrowlenginesutils@1.2.2
Detailed paths
-
Introduced through: Patrowl/PatrowlEngines@Patrowl/PatrowlEngines#ff378eaef199de1945d5ca0f2da9348f24da956f › patrowlenginesutils@1.2.2
AGPL-3.0 license
high severity
new
- Module: svn
- Introduced through: svn@1.0.1
Detailed paths
-
Introduced through: Patrowl/PatrowlEngines@Patrowl/PatrowlEngines#ff378eaef199de1945d5ca0f2da9348f24da956f › svn@1.0.1
GPL-2.0 license
medium severity
- Vulnerable module: werkzeug
- Introduced through: werkzeug@2.2.3 and flask@2.0.1
Detailed paths
-
Introduced through: Patrowl/PatrowlEngines@Patrowl/PatrowlEngines#ff378eaef199de1945d5ca0f2da9348f24da956f › werkzeug@2.2.3Remediation: Upgrade to werkzeug@3.0.6.
-
Introduced through: Patrowl/PatrowlEngines@Patrowl/PatrowlEngines#ff378eaef199de1945d5ca0f2da9348f24da956f › flask@2.0.1 › werkzeug@2.2.3Remediation: Upgrade to flask@2.0.1.
Overview
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling in formparser.MultiPartParser()
. An attacker can cause the parser to consume more memory than the upload size, in excess of max_form_memory_size
, by sending malicious data in a non-file field of a multipart/form-data
request.
Remediation
Upgrade werkzeug
to version 3.0.6 or higher.
References
medium severity
- Vulnerable module: zipp
- Introduced through: click@8.1.8, gunicorn@23.0.0 and others
Detailed paths
-
Introduced through: Patrowl/PatrowlEngines@Patrowl/PatrowlEngines#ff378eaef199de1945d5ca0f2da9348f24da956f › click@8.1.8 › importlib-metadata@6.7.0 › zipp@3.15.0
-
Introduced through: Patrowl/PatrowlEngines@Patrowl/PatrowlEngines#ff378eaef199de1945d5ca0f2da9348f24da956f › gunicorn@23.0.0 › importlib-metadata@6.7.0 › zipp@3.15.0
-
Introduced through: Patrowl/PatrowlEngines@Patrowl/PatrowlEngines#ff378eaef199de1945d5ca0f2da9348f24da956f › flask@2.0.1 › click@8.1.8 › importlib-metadata@6.7.0 › zipp@3.15.0
Overview
Affected versions of this package are vulnerable to Infinite loop where an attacker can cause the application to stop responding by initiating a loop through functions affecting the Path
module, such as joinpath
, the overloaded division operator, and iterdir
.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.
When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.
Two common types of DoS vulnerabilities:
High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.
Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm
ws
package
Remediation
Upgrade zipp
to version 3.19.1 or higher.
References
medium severity
- Vulnerable module: werkzeug
- Introduced through: werkzeug@2.2.3 and flask@2.0.1
Detailed paths
-
Introduced through: Patrowl/PatrowlEngines@Patrowl/PatrowlEngines#ff378eaef199de1945d5ca0f2da9348f24da956f › werkzeug@2.2.3Remediation: Upgrade to werkzeug@2.3.8.
-
Introduced through: Patrowl/PatrowlEngines@Patrowl/PatrowlEngines#ff378eaef199de1945d5ca0f2da9348f24da956f › flask@2.0.1 › werkzeug@2.2.3Remediation: Upgrade to flask@2.0.1.
Overview
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 CR
or LF
and is followed by megabytes of data without these characters.
Remediation
Upgrade werkzeug
to version 2.3.8, 3.0.1 or higher.
References
medium severity
- Vulnerable module: werkzeug
- Introduced through: werkzeug@2.2.3 and flask@2.0.1
Detailed paths
-
Introduced through: Patrowl/PatrowlEngines@Patrowl/PatrowlEngines#ff378eaef199de1945d5ca0f2da9348f24da956f › werkzeug@2.2.3Remediation: Upgrade to werkzeug@3.0.6.
-
Introduced through: Patrowl/PatrowlEngines@Patrowl/PatrowlEngines#ff378eaef199de1945d5ca0f2da9348f24da956f › flask@2.0.1 › werkzeug@2.2.3Remediation: Upgrade to flask@2.0.1.
Overview
Werkzeug is a WSGI web application library.
Affected versions of this package are vulnerable to Directory Traversal due to a bypass for os.path.isabs()
, which allows the improper handling of UNC paths beginning with /
, in the safe_join()
function. This allows an attacker to read some files on the affected server, if they are stored in an affected path.
Note: This is only exploitable on Windows systems using Python versions prior to 3.11.
Details
A Directory Traversal attack (also known as path traversal) aims to access files and directories that are stored outside the intended folder. By manipulating files with "dot-dot-slash (../)" sequences and its variations, or by using absolute file paths, it may be possible to access arbitrary files and directories stored on file system, including application source code, configuration, and other critical system files.
Directory Traversal vulnerabilities can be generally divided into two types:
- Information Disclosure: Allows the attacker to gain information about the folder structure or read the contents of sensitive files on the system.
st
is a module for serving static files on web pages, and contains a vulnerability of this type. In our example, we will serve files from the public
route.
If an attacker requests the following URL from our server, it will in turn leak the sensitive private key of the root user.
curl http://localhost:8080/public/%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/root/.ssh/id_rsa
Note %2e
is the URL encoded version of .
(dot).
- Writing arbitrary files: Allows the attacker to create or replace existing files. This type of vulnerability is also known as
Zip-Slip
.
One way to achieve this is by using a malicious zip
archive that holds path traversal filenames. When each filename in the zip archive gets concatenated to the target extraction folder, without validation, the final path ends up outside of the target folder. If an executable or a configuration file is overwritten with a file containing malicious code, the problem can turn into an arbitrary code execution issue quite easily.
The following is an example of a zip
archive with one benign file and one malicious file. Extracting the malicious file will result in traversing out of the target folder, ending up in /root/.ssh/
overwriting the authorized_keys
file:
2018-04-15 22:04:29 ..... 19 19 good.txt
2018-04-15 22:04:42 ..... 20 20 ../../../../../../root/.ssh/authorized_keys
Remediation
Upgrade Werkzeug
to version 3.0.6 or higher.
References
medium severity
new
- Module: nose
- Introduced through: nose@1.3.7 and svn@1.0.1
Detailed paths
-
Introduced through: Patrowl/PatrowlEngines@Patrowl/PatrowlEngines#ff378eaef199de1945d5ca0f2da9348f24da956f › nose@1.3.7
-
Introduced through: Patrowl/PatrowlEngines@Patrowl/PatrowlEngines#ff378eaef199de1945d5ca0f2da9348f24da956f › svn@1.0.1 › nose@1.3.7
LGPL-2.1 license