Exposure of Data Element to Wrong Session Affecting openshift-clients-redistributable package, versions <0:4.13.0-202305312300.p0.g05d83ef.assembly.stream.el8
Threat Intelligence
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk ID SNYK-RHEL8-OPENSHIFTCLIENTSREDISTRIBUTABLE-6182058
- published 20 Jan 2024
- disclosed 5 May 2023
Introduced: 5 May 2023
CVE-2023-30861 Open this link in a new tabHow to fix?
Upgrade RHEL:8 openshift-clients-redistributable to version 0:4.13.0-202305312300.p0.g05d83ef.assembly.stream.el8 or higher.
This issue was patched in RHSA-2023:3536.
NVD Description
Note: Versions mentioned in the description apply only to the upstream openshift-clients-redistributable package and not the openshift-clients-redistributable package as distributed by RHEL.
See How to fix? for RHEL:8 relevant fixed versions and status.
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 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.
References
- https://access.redhat.com/security/cve/CVE-2023-30861
- https://github.com/pallets/flask/commit/70f906c51ce49c485f1d355703e9cc3386b1cc2b
- https://github.com/pallets/flask/commit/afd63b16170b7c047f5758eb910c416511e9c965
- https://github.com/pallets/flask/releases/tag/2.2.5
- https://github.com/pallets/flask/releases/tag/2.3.2
- https://github.com/pallets/flask/security/advisories/GHSA-m2qf-hxjv-5gpq
- https://www.debian.org/security/2023/dsa-5442
- https://security.netapp.com/advisory/ntap-20230818-0006/
- https://lists.debian.org/debian-lts-announce/2023/08/msg00024.html