Advisory

PYSEC-2023-62

Also known as: CVE-2023-30861, GHSA-m2qf-hxjv-5gpq

Summary

The record has no summary.

Details

Flask is a lightweight WSGI web application framework. When all of the following conditions are met, a response containing data intended for one client may be cached and subsequently sent by the 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.

  1. The application must be 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 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.

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. This issue has been fixed in versions 2.3.2 and 2.2.5.

Severity

Not rated by the source.

Dates

Published
2023-05-02 18:15 UTC
Modified
2023-11-08 04:12 UTC

Affected packages and fixes

flask

PyPI · All systems

Affected

  • introduced 0, fixed 2.2.5, introduced 2.3.0, fixed 2.3.2 (ecosystem)

Fixed versions

2.2.5, 2.3.2

Fix

  • Fixed version 2.2.5
    pip install --upgrade flask==2.2.5
  • Fixed version 2.3.2
    pip install --upgrade flask==2.3.2

Fix 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

View this record on OSV.dev

Source

Source: PyPA Advisory Database · CC BY 4.0

Sources & licences