Vulnerabilities

 3 via 5 paths

Dependencies

 22

Source

 GitHub

Commit

 3589c5c4

Find, fix and prevent vulnerabilities in your code.

Test and protect my applications
Severity
  • 2
  • 1
Status
  • 3
  • 0
  • 0

medium severity

Denial of Service (DoS)

  • Vulnerable module: jwcrypto
  • Introduced through: jwcrypto@1.5.2 and python-jwt@4.1.0

Detailed paths

  • Introduced through: larsw/flask-oidc-ex@larsw/flask-oidc-ex#3589c5c4e57af5f166de2344e7c1666a14dee4a7 › jwcrypto@1.5.2
    Remediation: Upgrade to jwcrypto@1.5.6.
  • Introduced through: larsw/flask-oidc-ex@larsw/flask-oidc-ex#3589c5c4e57af5f166de2344e7c1666a14dee4a7 › python-jwt@4.1.0 › jwcrypto@1.5.2

Overview

Affected versions of this package are vulnerable to Denial of Service (DoS) due to the deserialize function. An attacker can cause a denial of service by passing in a malicious JWE Token with a high compression ratio. When the server processes this token, it will consume a lot of memory and processing time.

Workaround

This vulnerability can be mitigated by limiting the maximum token length to 250K.

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 jwcrypto to version 1.5.6 or higher.

References

Denial of Service (DoS) vulnerability report

medium severity

Inefficient Algorithmic Complexity

  • Vulnerable module: werkzeug
  • Introduced through: flask@2.2.5

Detailed paths

  • Introduced through: larsw/flask-oidc-ex@larsw/flask-oidc-ex#3589c5c4e57af5f166de2344e7c1666a14dee4a7 › flask@2.2.5 › werkzeug@2.2.3
    Remediation: Upgrade to flask@2.2.5.

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

low severity
new

Uncontrolled Resource Consumption ('Resource Exhaustion')

  • Vulnerable module: cryptography
  • Introduced through: jwcrypto@1.5.2 and python-jwt@4.1.0

Detailed paths

  • Introduced through: larsw/flask-oidc-ex@larsw/flask-oidc-ex#3589c5c4e57af5f166de2344e7c1666a14dee4a7 › jwcrypto@1.5.2 › cryptography@42.0.5
  • Introduced through: larsw/flask-oidc-ex@larsw/flask-oidc-ex#3589c5c4e57af5f166de2344e7c1666a14dee4a7 › python-jwt@4.1.0 › jwcrypto@1.5.2 › cryptography@42.0.5

Overview

Affected versions of this package are vulnerable to Uncontrolled Resource Consumption ('Resource Exhaustion') due to the session cache entering an incorrect state and failing to flush properly as it fills, leading to uncontrolled memory consumption. This condition is triggered under certain server configurations when processing TLSv1.3 sessions. Specifically, this occurs if the non-default SSL_OP_NO_TICKET option is enabled, but not if early_data support is configured along with the default anti-replay protection. A malicious client could deliberately create this scenario to force a service disruption. It may also occur accidentally in normal operation.

Note:

This issue is only exploitable if the server supports TLSv1.3 and is configured with the SSL_OP_NO_TICKET option enabled.

Remediation

A fix was pushed into the master branch but not yet published.

References

Uncontrolled Resource Consumption ('Resource Exhaustion') vulnerability report