Homepage

flask@0.5.1 vulnerabilities

A simple framework for building complex web applications.

  • latest version

    3.1.3

  • latest non vulnerable version

    3.1.3

  • first published

    15 years ago

  • latest version published

    19 days ago

  • licenses detected

  • View flask package health on Snyk Advisor  (opens in a new tab)
    • Go back to all versions of this package
    Report a new vulnerability Found a mistake?

    Direct Vulnerabilities

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

    Fix vulnerabilities automatically

    Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

    Fix for free
    VulnerabilityVulnerable Version
    • L
    Use of Cache Containing Sensitive Information

    Affected versions of this package are vulnerable to Use of Cache Containing Sensitive Information in the session object. An attacker can cause sensitive user-specific responses to be cached and served to other users by leveraging a caching proxy that does not ignore responses with cookies, when the application does not set a Cache-Control header and accesses the session only for keys without mutating or accessing values.

    Note:

    This is only exploitable if the application is hosted behind a caching proxy that does not ignore responses with cookies, does not set a Cache-Control header to indicate that a page is private or should not be cached, and accesses the session in a way that does not access the values, only the keys, and does not mutate the session.

    How to fix Use of Cache Containing Sensitive Information?

    Upgrade flask to version 3.1.3 or higher.

    [,3.1.3)
    • H
    Information Exposure

    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.

    How to fix Information Exposure?

    Upgrade flask to version 2.2.5, 2.3.2 or higher.

    [,2.2.5)[2.3.0,2.3.2)
    • H
    Denial of Service (DoS)

    Flask is a lightweight WSGI web application framework

    Affected versions of this package are vulnerable to Denial of Service (DoS). The package allows for unsafe encoded JSON data to be decoded.

    How to fix Denial of Service (DoS)?

    Upgrade Flask to version 0.12.3 or higher.

    [,0.12.3)
    • H
    Improper Input Validation

    flask is a lightweight WSGI web application framework.

    Affected versions of this package are vulnerable to Improper Input Validation. It did not detect the encoding of incoming JSON data as one of the supported UTF encodings, and allowed arbitrary encodings from the request.

    How to fix Improper Input Validation?

    Upgrade flask to version 0.12.3 or higher.

    [,0.12.3)
    • L
    Arbitrary File Download

    Affected versions of flask are vulnerable to Arbitrary File Download. A client can use backslashes to escape the directory the files where exposed from. Note: Only if the host server is a windows based operating system.

    [,0.6.1)
    Go back to all versions of this package