Skip to main content

Test Results

mostafa/grest

Vulnerabilities

 14 via 52 paths

Dependencies

 47

Source

 GitHub

Commit

 2716a326

Find, fix and prevent vulnerabilities in your code.

Test and protect my applications
Issue type
  • 14
  • 4
Severity
  • 7
  • 10
  • 1
Status
  • 18
  • 0
  • 0

high severity

Command Injection

  • Vulnerable module: cookiecutter
  • Introduced through: cookiecutter@1.7.3

Detailed paths

  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › cookiecutter@1.7.3
    Remediation: Upgrade to cookiecutter@2.1.1.

Overview

cookiecutter is a command-line utility that creates projects from cookiecutters.

Affected versions of this package are vulnerable to Command Injection via hg argument injection. When calling the cookiecutter function from Python code with the checkout parameter, it is passed to the hg checkout command in a way that additional flags can be set. The additional flags can be used to perform a command injection.

PoC

from cookiecutter.main import cookiecutter

checkout = "--config=alias.checkout=!touch ./HELLO"
cookiecutter('some valid hg repository', checkout=checkout)

Remediation

Upgrade cookiecutter to version 2.1.1 or higher.

References

Command Injection vulnerability report

high severity

Information Exposure

  • Vulnerable module: flask
  • Introduced through: flask@2.0.1, flask-classful@0.14.2 and others

Detailed paths

  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › flask@2.0.1
    Remediation: Upgrade to flask@2.2.5.
  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › flask-classful@0.14.2 › flask@2.0.1
    Remediation: Upgrade to flask-classful@0.14.2.
  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › pytest-flask@1.2.0 › flask@2.0.1
    Remediation: Upgrade to pytest-flask@1.2.0.

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:

  1. The application is 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 is 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.

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

Information Exposure vulnerability report

high severity

Improper Control of Generation of Code ('Code Injection')

  • Vulnerable module: setuptools
  • Introduced through: setuptools@57.0.0

Detailed paths

  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › setuptools@57.0.0
    Remediation: 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

Improper Control of Generation of Code ('Code Injection') vulnerability report

high severity

Denial of Service (DoS)

  • Vulnerable module: werkzeug
  • Introduced through: werkzeug@2.0.1, flask@2.0.1 and others

Detailed paths

  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › werkzeug@2.0.1
    Remediation: Upgrade to werkzeug@2.2.3.
  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › flask@2.0.1 › werkzeug@2.0.1
    Remediation: Upgrade to flask@2.0.1.
  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › pytest-flask@1.2.0 › werkzeug@2.0.1
    Remediation: Upgrade to pytest-flask@1.2.0.
  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › flask-classful@0.14.2 › flask@2.0.1 › werkzeug@2.0.1
    Remediation: Upgrade to flask-classful@0.14.2.
  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › pytest-flask@1.2.0 › flask@2.0.1 › werkzeug@2.0.1
    Remediation: Upgrade to pytest-flask@1.2.0.

…and 2 more

Overview

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 request.data, request.form, request.files, or request.get_data(parse_form_data=False), consuming CPU, memory, or file handles resources. The amount of CPU time required can block worker processes from handling other requests. The amount of RAM required can trigger an out-of-memory and crash the process.

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 werkzeug to version 2.2.3 or higher.

References

Denial of Service (DoS) vulnerability report

high severity

Remote Code Execution (RCE)

  • Vulnerable module: werkzeug
  • Introduced through: werkzeug@2.0.1, flask@2.0.1 and others

Detailed paths

  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › werkzeug@2.0.1
    Remediation: Upgrade to werkzeug@3.0.3.
  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › flask@2.0.1 › werkzeug@2.0.1
    Remediation: Upgrade to flask@2.0.1.
  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › pytest-flask@1.2.0 › werkzeug@2.0.1
    Remediation: Upgrade to pytest-flask@1.2.0.
  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › flask-classful@0.14.2 › flask@2.0.1 › werkzeug@2.0.1
    Remediation: Upgrade to flask-classful@0.14.2.
  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › pytest-flask@1.2.0 › flask@2.0.1 › werkzeug@2.0.1
    Remediation: Upgrade to pytest-flask@1.2.0.

…and 2 more

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

Remote Code Execution (RCE) vulnerability report

high severity

GPL-2.0 license

  • Module: dicttoxml
  • Introduced through: dicttoxml@1.7.4

Detailed paths

  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › dicttoxml@1.7.4

GPL-2.0 license

GPL-2.0 license vulnerability report

high severity

GPL-2.0 license

  • Module: unidecode
  • Introduced through: unidecode@1.2.0

Detailed paths

  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › unidecode@1.2.0

GPL-2.0 license

GPL-2.0 license vulnerability report

medium severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: werkzeug
  • Introduced through: werkzeug@2.0.1, flask@2.0.1 and others

Detailed paths

  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › werkzeug@2.0.1
    Remediation: Upgrade to werkzeug@3.0.6.
  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › flask@2.0.1 › werkzeug@2.0.1
    Remediation: Upgrade to flask@2.0.1.
  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › pytest-flask@1.2.0 › werkzeug@2.0.1
    Remediation: Upgrade to pytest-flask@1.2.0.
  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › flask-classful@0.14.2 › flask@2.0.1 › werkzeug@2.0.1
    Remediation: Upgrade to flask-classful@0.14.2.
  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › pytest-flask@1.2.0 › flask@2.0.1 › werkzeug@2.0.1
    Remediation: Upgrade to pytest-flask@1.2.0.

…and 2 more

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

Allocation of Resources Without Limits or Throttling vulnerability report

medium severity

Infinite loop

  • Vulnerable module: zipp
  • Introduced through: pytest@6.2.4, cookiecutter@1.7.3 and others

Detailed paths

  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › pytest@6.2.4 › importlib-metadata@6.7.0 › zipp@3.15.0
    Remediation: Upgrade to pytest@7.4.1.
  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › cookiecutter@1.7.3 › click@8.1.8 › importlib-metadata@6.7.0 › zipp@3.15.0
  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › flask@2.0.1 › click@8.1.8 › importlib-metadata@6.7.0 › zipp@3.15.0
  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › pytest@6.2.4 › attrs@24.2.0 › importlib-metadata@6.7.0 › zipp@3.15.0
    Remediation: Upgrade to pytest@7.4.1.
  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › pytest@6.2.4 › pluggy@0.13.1 › importlib-metadata@6.7.0 › zipp@3.15.0
    Remediation: Upgrade to pytest@7.4.1.
  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › pytest-flask@1.2.0 › pytest@6.2.4 › importlib-metadata@6.7.0 › zipp@3.15.0
    Remediation: Upgrade to pytest-flask@1.3.0.
  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › flask-classful@0.14.2 › flask@2.0.1 › click@8.1.8 › importlib-metadata@6.7.0 › zipp@3.15.0
  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › pytest-flask@1.2.0 › flask@2.0.1 › click@8.1.8 › importlib-metadata@6.7.0 › zipp@3.15.0
  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › pytest-flask@1.2.0 › pytest@6.2.4 › attrs@24.2.0 › importlib-metadata@6.7.0 › zipp@3.15.0
    Remediation: Upgrade to pytest-flask@1.3.0.
  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › pytest-flask@1.2.0 › pytest@6.2.4 › pluggy@0.13.1 › importlib-metadata@6.7.0 › zipp@3.15.0
    Remediation: Upgrade to pytest-flask@1.3.0.

…and 7 more

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

Infinite loop vulnerability report

medium severity

Inefficient Algorithmic Complexity

  • Vulnerable module: werkzeug
  • Introduced through: werkzeug@2.0.1, flask@2.0.1 and others

Detailed paths

  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › werkzeug@2.0.1
    Remediation: Upgrade to werkzeug@2.3.8.
  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › flask@2.0.1 › werkzeug@2.0.1
    Remediation: Upgrade to flask@2.0.1.
  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › pytest-flask@1.2.0 › werkzeug@2.0.1
    Remediation: Upgrade to pytest-flask@1.2.0.
  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › flask-classful@0.14.2 › flask@2.0.1 › werkzeug@2.0.1
    Remediation: Upgrade to flask-classful@0.14.2.
  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › pytest-flask@1.2.0 › flask@2.0.1 › werkzeug@2.0.1
    Remediation: Upgrade to pytest-flask@1.2.0.

…and 2 more

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

Inefficient Algorithmic Complexity vulnerability report

medium severity

Directory Traversal

  • Vulnerable module: werkzeug
  • Introduced through: werkzeug@2.0.1, flask@2.0.1 and others

Detailed paths

  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › werkzeug@2.0.1
    Remediation: Upgrade to werkzeug@3.0.6.
  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › flask@2.0.1 › werkzeug@2.0.1
    Remediation: Upgrade to flask@2.0.1.
  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › pytest-flask@1.2.0 › werkzeug@2.0.1
    Remediation: Upgrade to pytest-flask@1.2.0.
  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › flask-classful@0.14.2 › flask@2.0.1 › werkzeug@2.0.1
    Remediation: Upgrade to flask-classful@0.14.2.
  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › pytest-flask@1.2.0 › flask@2.0.1 › werkzeug@2.0.1
    Remediation: Upgrade to pytest-flask@1.2.0.

…and 2 more

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

Directory Traversal vulnerability report

medium severity

Resource Exhaustion

  • Vulnerable module: idna
  • Introduced through: requests@2.25.1 and cookiecutter@1.7.3

Detailed paths

  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › requests@2.25.1 › idna@2.10
    Remediation: Upgrade to requests@2.32.0.
  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › cookiecutter@1.7.3 › requests@2.25.1 › idna@2.10
    Remediation: Upgrade to cookiecutter@2.3.1.

Overview

Affected versions of this package are vulnerable to Resource Exhaustion via the idna.encode function. An attacker can consume significant resources and potentially cause a denial-of-service by supplying specially crafted arguments to this function.

Note: This is triggered by arbitrarily large inputs that would not occur in normal usage but may be passed to the library assuming there is no preliminary input validation by the higher-level application.

Remediation

Upgrade idna to version 3.7 or higher.

References

Resource Exhaustion vulnerability report

medium severity

Information Exposure

  • Vulnerable module: requests
  • Introduced through: requests@2.25.1 and cookiecutter@1.7.3

Detailed paths

  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › requests@2.25.1
    Remediation: Upgrade to requests@2.31.0.
  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › cookiecutter@1.7.3 › requests@2.25.1
    Remediation: Upgrade to cookiecutter@2.3.1.

Overview

Affected versions of this package are vulnerable to Information Exposure by leaking Proxy-Authorization headers to destination servers during redirects to an HTTPS origin. This is a result of how rebuild_proxies is used to recompute and reattach the Proxy-Authorization header to requests when redirected.

NOTE: This behavior has only been observed to affect proxied requests when credentials are supplied in the URL user information component (e.g. https://username:password@proxy:8080), and only when redirecting to HTTPS:

  1. HTTP → HTTPS: leak

  2. HTTPS → HTTP: no leak

  3. HTTPS → HTTPS: leak

  4. HTTP → HTTP: no leak

For HTTP connections sent through the proxy, the proxy will identify the header in the request and remove it prior to forwarding to the destination server. However when sent over HTTPS, the Proxy-Authorization header must be sent in the CONNECT request as the proxy has no visibility into further tunneled requests. This results in Requests forwarding the header to the destination server unintentionally, allowing a malicious actor to potentially exfiltrate those credentials.

Workaround

This vulnerability can be avoided by setting allow_redirects to False on all calls through Requests top-level APIs, and then capturing the 3xx response codes to make a new request to the redirect destination.

Remediation

Upgrade requests to version 2.31.0 or higher.

References

Information Exposure vulnerability report

medium severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: setuptools
  • Introduced through: setuptools@57.0.0

Detailed paths

  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › setuptools@57.0.0
    Remediation: Upgrade to setuptools@65.5.1.

Overview

Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) via crafted HTML package or custom PackageIndex page.

Note:

Only a small portion of the user base is impacted by this flaw. Setuptools maintainers pointed out that package_index is deprecated (not formally, but “in spirit”) and the vulnerability isn't reachable through standard, recommended workflows.

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.

The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.

Let’s take the following regular expression as an example:

regex = /A(B|C+)+D/

This regular expression accomplishes the following:

  • A The string must start with the letter 'A'
  • (B|C+)+ The string must then follow the letter A with either the letter 'B' or some number of occurrences of the letter 'C' (the + matches one or more times). The + at the end of this section states that we can look for one or more matches of this section.
  • D Finally, we ensure this section of the string ends with a 'D'

The expression would match inputs such as ABBD, ABCCCCD, ABCBCCCD and ACCCCCD

It most cases, it doesn't take very long for a regex engine to find a match:

$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
0.04s user 0.01s system 95% cpu 0.052 total

$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
1.79s user 0.02s system 99% cpu 1.812 total

The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.

Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.

Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:

  1. CCC
  2. CC+C
  3. C+CC
  4. C+C+C.

The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.

From there, the number of steps the engine must use to validate a string just continues to grow.

String Number of C's Number of steps
ACCCX 3 38
ACCCCX 4 71
ACCCCCX 5 136
ACCCCCCCCCCCCCCX 14 65,553

By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.

Remediation

Upgrade setuptools to version 65.5.1 or higher.

References

Regular Expression Denial of Service (ReDoS) vulnerability report

medium severity

Always-Incorrect Control Flow Implementation

  • Vulnerable module: requests
  • Introduced through: requests@2.25.1 and cookiecutter@1.7.3

Detailed paths

  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › requests@2.25.1
    Remediation: Upgrade to requests@2.32.2.
  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › cookiecutter@1.7.3 › requests@2.25.1
    Remediation: Upgrade to cookiecutter@2.3.1.

Overview

Affected versions of this package are vulnerable to Always-Incorrect Control Flow Implementation when making requests through a Requests Session. An attacker can bypass certificate verification by making the first request with verify=False, causing all subsequent requests to ignore certificate verification regardless of changes to the verify value.

Notes:

  1. For requests <2.32.0, avoid setting verify=False for the first request to a host while using a Requests Session.

  2. For requests <2.32.0, call close() on Session objects to clear existing connections if verify=False is used.

  3. This vulnerability was initially fixed in version 2.32.0, which was yanked. Therefore, the next available fixed version is 2.32.2.

Remediation

Upgrade requests to version 2.32.2 or higher.

References

Always-Incorrect Control Flow Implementation vulnerability report

medium severity

MPL-2.0 license

  • Module: certifi
  • Introduced through: requests@2.25.1 and cookiecutter@1.7.3

Detailed paths

  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › requests@2.25.1 › certifi@2025.1.31
  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › cookiecutter@1.7.3 › requests@2.25.1 › certifi@2025.1.31

MPL-2.0 license

MPL-2.0 license vulnerability report

medium severity

LGPL-2.1 license

  • Module: chardet
  • Introduced through: requests@2.25.1 and cookiecutter@1.7.3

Detailed paths

  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › requests@2.25.1 › chardet@4.0.0
  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › cookiecutter@1.7.3 › binaryornot@0.4.4 › chardet@4.0.0
  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › cookiecutter@1.7.3 › requests@2.25.1 › chardet@4.0.0

LGPL-2.1 license

LGPL-2.1 license vulnerability report

low severity

Access Restriction Bypass

  • Vulnerable module: werkzeug
  • Introduced through: werkzeug@2.0.1, flask@2.0.1 and others

Detailed paths

  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › werkzeug@2.0.1
    Remediation: Upgrade to werkzeug@2.2.3.
  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › flask@2.0.1 › werkzeug@2.0.1
    Remediation: Upgrade to flask@2.0.1.
  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › pytest-flask@1.2.0 › werkzeug@2.0.1
    Remediation: Upgrade to pytest-flask@1.2.0.
  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › flask-classful@0.14.2 › flask@2.0.1 › werkzeug@2.0.1
    Remediation: Upgrade to flask-classful@0.14.2.
  • Introduced through: mostafa/grest@mostafa/grest#2716a326a04ea00d4c2f5d9ced53da1b89a5fb25 › pytest-flask@1.2.0 › flask@2.0.1 › werkzeug@2.0.1
    Remediation: Upgrade to pytest-flask@1.2.0.

…and 2 more

Overview

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 =value instead of key=value and have them accepted by the affected browser. For example, a cookie like =__Host-test=bad would be parsed as __Host-test=bad and the key treated as valid while the value is ignored.

Remediation

Upgrade werkzeug to version 2.2.3 or higher.

References

Access Restriction Bypass vulnerability report