[Snyk:High] flask Information Exposure (due by 06/09/2023)

[cnlucas]

Introduced through
flask@2.1.2, flask-apispec@0.7.0 and others
Fixed in
flask@2.2.5, @2.3.2

Exploit maturity
No known exploit

Detailed paths and remediation

Introduced through: project@0.0.0 › flask@2.1.2
Fix: Upgrade flask to version 2.2.5 or 2.3.2

Introduced through: project@0.0.0 › flask-apispec@0.7.0 › flask@2.1.2
Fix: Pin flask to version 2.2.5 or 2.3.2
Introduced through: project@0.0.0 › flask-cors@3.0.10 › flask@2.1.2
Fix: Pin flask to version 2.2.5 or 2.3.2

…and 2 more
Security information
Factors contributing to the scoring:

Snyk: [CVSS 7.5](https://security.snyk.io/vuln/SNYK-PYTHON-FLASK-5490129) - High Severity
NVD: Not available. NVD has not yet published its analysis.

Why are the scores different? Learn how Snyk evaluates vulnerability scores
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.

Action items:

• Pin flask to version 2.2.5 or 2.3.2

Completion criteria:

• Vulnerability is no longer flagged by snyk