gunicorn@20.0.2 vulnerabilities

WSGI HTTP Server for UNIX

  • latest version

    23.0.0

  • latest non vulnerable version

  • first published

    15 years ago

  • latest version published

    8 months ago

  • licenses detected

  • Direct Vulnerabilities

    Known vulnerabilities in the gunicorn package. This does not include vulnerabilities belonging to this package’s dependencies.

    How to fix?

    Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.

    Fix for free
    VulnerabilityVulnerable Version
    • H
    HTTP Request Smuggling

    gunicorn is a Python WSGI HTTP Server for UNIX

    Affected versions of this package are vulnerable to HTTP Request Smuggling due to improper validation of the Transfer-Encoding header. An attacker can manipulate session data, poison caches, or compromise data integrity by exploiting the fallback to Content-Length when Transfer-Encoding is not correctly handled.

    How to fix HTTP Request Smuggling?

    Upgrade gunicorn to version 23.0.0 or higher.

    [,23.0.0)
    • L
    Improper Check for Unusual or Exceptional Conditions

    gunicorn is a Python WSGI HTTP Server for UNIX

    Affected versions of this package are vulnerable to Improper Check for Unusual or Exceptional Conditions due to the use of time.time() in worker timeout logic, which may be wrong. An attacker who can control the system time can force a worker to time out.

    How to fix Improper Check for Unusual or Exceptional Conditions?

    Upgrade gunicorn to version 21.2.0 or higher.

    [,21.2.0)
    • H
    HTTP Request Smuggling

    gunicorn is a Python WSGI HTTP Server for UNIX

    Affected versions of this package are vulnerable to HTTP Request Smuggling due to the improper validation of Transfer-Encoding headers. An attacker can bypass security restrictions and access restricted endpoints by crafting requests with conflicting Transfer-Encoding headers.

    Notes:

    1. This is only exploitable if users have a network path which does not filter out invalid requests;

    2. Users are advised to block access to restricted endpoints via a firewall or other mechanism until a fix can be developed.

    3. This issue arises from the application's incorrectly processing of requests with multiple, conflicting Transfer-Encoding headers, treating them as chunked regardless of the final encoding specified.

    How to fix HTTP Request Smuggling?

    Upgrade gunicorn to version 22.0.0 or higher.

    [,22.0.0)