Most recent entries from all

bdu:2023-02381

BREW-aws-sam-cli-CVE-2023-30861 — Flask vulnerable to possible disclosure of permanent session cookie due to missing Vary: Cookie header

Affected: Homebrew: aws-sam-cli

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.

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`](https://flask.palletsprojects.com/en/2.3.x/api/#flask.session.permanent). 2. The application does not access or modify the session at any point during a request. 4. [`SESSION_REFRESH_EACH_REQUEST`](https://flask.palletsprojects.com/en/2.3.x/config/#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.

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.

certfr-2023-avi-0484 — De multiples vulnérabilités ont été découvertes dans les produits IBM. Certaines d'entre el…

certfr-2023-avi-0484

EUVD-2026-216436

fkie_cve-2023-30861

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.

GHSA-m2qf-hxjv-5gpq — Flask vulnerable to possible disclosure of permanent session cookie due to missing Vary: Cookie header

Affected: PyPI: Flask

gsd-2023-30861

OESA-2023-1922 — python-flask security update

Affected: openEuler:20.03-LTS-SP1: python-flask, openEuler:20.03-LTS-SP3: python-flask, openEuler:22.03-LTS: python-flask, openEuler:22.03-LTS-SP1: python-flask, openEuler:22.03-LTS-SP2: python-flask

Flask is a lightweight WSGI web application framework. It is designed to make getting started quick and easy, with the ability to scale up to complex applications. It began as a simple wrapper around Werkzeug and Jinja and has become one of the most popular Python web application frameworks. Security Fix(es): 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 fix…

openSUSE-SU-2024:12923-1 — python310-Flask-2.2.5-1.1 on GA media

python310-Flask-2.2.5-1.1 on GA media

PYSEC-2023-62

Affected: PyPI: flask

RHSA-2023:3440 — Red Hat Security Advisory: Red Hat OpenStack Platform 17.0 (python-flask) security update

flask: Possible disclosure of permanent session cookie due to missing Vary: Cookie header

SUSE-SU-2023:2263-2 — Security update for python-Flask

Security update for python-Flask

UBUNTU-CVE-2023-30861

Affected: Ubuntu:20.04:LTS: flask, Ubuntu:22.04:LTS: flask

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.

WID-SEC-W-2023-1373 — Red Hat OpenStack Platform : Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in der Red Hat OpenStack Platform ausnutzen, um seine Privilegien zu erhöhen, einen Denial of Service zu verursachen oder Informationen offenzulegen.