flask
Affected
- introduced
2.3.0, fixed2.3.2(ecosystem)
Fixed versions
2.3.2
Fix
- Fixed version
2.3.2pip install --upgrade flask==2.3.2
Advisory
Also known as: CVE-2023-30861, PYSEC-2023-62
Flask vulnerable to possible disclosure of permanent session cookie due to missing Vary: Cookie header
When all of the following conditions are met, a response containing data intended for one client may be cached and subsequently sent by a proxy to other clients. If the proxy also caches Set-Cookie headers, it may send one client's session cookie to other clients. The severity depends on the application's use of the session, and the proxy's behavior regarding cookies. The risk depends on _all_ these conditions being met.
Cache-Control header to indicate that a page is private or should not be cached.This happens because vulnerable versions of Flask only set the Vary: Cookie header when the session is accessed or modified, not when it is refreshed (re-sent to update the expiration) without being accessed or modified.
High Basis: The source's own band: HIGH
2.3.0, fixed 2.3.2 (ecosystem)2.3.2
2.3.2pip install --upgrade flask==2.3.20, fixed 2.2.5 (ecosystem)2.2.5
2.2.5pip install --upgrade flask==2.2.5Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0