Описание
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.
- The application must be 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_REQUESTenabled (the default).- The application does not set a
Cache-Controlheader to indicate that a page is private or should not be cached. This happens because vulnerable versions of Flask only set theVary: Cookieheader 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.
A flaw was found in the Python Flask package. A cached response may contain data for one client sent by a proxy to other clients, including session cookies, resulting in the compromise of data confidentiality contained in the leak requests or cookies. This happens when the following conditions are met by the proxy's behavior regarding cookies and the application's behavior session usage: - The caching proxy does not strip or ignore response with cookies
- The application sets a permanent session
- The application does not access or modify the session during requests
- SESSION_REFRESH_EACH_REQUEST is enabled, which is the default Flask behavior
- The application does not set the Cache-Control header to avoid being cached
Затронутые пакеты
| Платформа | Пакет | Состояние | Рекомендация | Релиз |
|---|---|---|---|---|
| Red Hat Ceph Storage 3 | python-flask | Out of support scope | ||
| Red Hat Ceph Storage 7 | python-flask | Affected | ||
| Red Hat Enterprise Linux 8 | python-flask | Affected | ||
| Red Hat Storage 3 | python-flask | Affected | ||
| Ironic content for Red Hat OpenShift Container Platform 4.11 | python-flask | Fixed | RHSA-2023:3541 | 14.06.2023 |
| Ironic content for Red Hat OpenShift Container Platform 4.12 | python-flask | Fixed | RHSA-2023:3545 | 14.06.2023 |
| Ironic content for Red Hat OpenShift Container Platform 4.13 | python-flask | Fixed | RHSA-2023:3536 | 13.06.2023 |
| Red Hat Enterprise Linux 7 Extras | python-flask | Fixed | RHSA-2023:3525 | 07.06.2023 |
| Red Hat OpenStack Platform 16.1 | python-flask | Fixed | RHSA-2023:3446 | 05.06.2023 |
| Red Hat OpenStack Platform 16.2 | python-flask | Fixed | RHSA-2023:3444 | 05.06.2023 |
Показывать по
Дополнительная информация
Статус:
7.5 High
CVSS3
Связанные уязвимости
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` head...
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` heade
Flask is a lightweight WSGI web application framework. When all of the ...
7.5 High
CVSS3