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.

The remote Redhat Enterprise Linux 8 / 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2023:3536 advisory.

  - golang: net/http, net/textproto: denial of service from excessive memory allocation (CVE-2023-24534)

  - golang: net/http, net/textproto, mime/multipart: denial of service from excessive resource consumption     (CVE-2023-24536)

  - golang: go/parser: Infinite loop in parsing (CVE-2023-24537)

  - golang: html/template: backticks not treated as string delimiters (CVE-2023-24538)

  - flask: Possible disclosure of permanent session cookie due to missing Vary: Cookie header (CVE-2023-30861)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Redhat Enterprise Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2023:3541 advisory.

  - cri-o: incorrect handling of the supplementary groups (CVE-2022-2995)

  - flask: Possible disclosure of permanent session cookie due to missing Vary: Cookie header (CVE-2023-30861)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Redhat Enterprise Linux 8 host has a package installed that is affected by a vulnerability as referenced in the RHSA-2023:3444 advisory.

    Flask is called a micro-framework because the idea to keep the core     simple but extensible. There is no database abstraction layer, no form     validation or anything else where different libraries already exist that     can handle that. However Flask knows the concept of extensions that can add     this functionality into your application as if it was implemented in Flask     itself. There are currently extensions for object relational mappers, form     validation, upload handling, various open authentication technologies and     more.

    Security Fix(es):

    * Possible disclosure of permanent session cookie due to missing Vary:
    Cookie header (CVE-2023-30861)

    For more details about the security issue(s), including the impact, a CVSS     score, acknowledgments, and other related information, refer to the CVE     page listed in the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote Redhat Enterprise Linux 8 host has a package installed that is affected by a vulnerability as referenced in the RHSA-2023:3446 advisory.

    Flask is called a micro-framework because the idea to keep the core     simple but extensible. There is no database abstraction layer, no form     validation or anything else where different libraries already exist that     can handle that. However Flask knows the concept of extensions that can add     this functionality into your application as if it was implemented in Flask     itself. There are currently extensions for object relational mappers, form     validation, upload handling, various open authentication technologies and     more.

    Security Fix(es):

    * Possible disclosure of permanent session cookie due to missing Vary:
    Cookie header (CVE-2023-30861)

    For more details about the security issue(s), including the impact, a CVSS     score, acknowledgments, and other related information, refer to the CVE     page listed in the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote Redhat Enterprise Linux 9 host has a package installed that is affected by a vulnerability as referenced in the RHSA-2023:3440 advisory.

    Flask is called a micro-framework because the idea to keep the core     simple but extensible. There is no database abstraction layer, no form     validation or anything else where different libraries already exist that     can handle that. However Flask knows the concept of extensions that can add     this functionality into your application as if it was implemented in Flask     itself. There are currently extensions for object relational mappers, form     validation, upload handling, various open authentication technologies and     more.

    Security Fix(es):

    * Possible disclosure of permanent session cookie due to missing Vary:
    Cookie header (CVE-2023-30861)

    For more details about the security issue(s), including the impact, a CVSS     score, acknowledgments, and other related information, refer to the CVE     page listed in the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote Redhat Enterprise Linux 8 / 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2023:3545 advisory.

  - golang: html/template: improper handling of JavaScript whitespace (CVE-2023-24540)

  - flask: Possible disclosure of permanent session cookie due to missing Vary: Cookie header (CVE-2023-30861)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Red Hat Enterprise Linux CoreOS 4 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2023:3536 advisory.

  - HTTP and MIME header parsing can allocate large amounts of memory, even when parsing small inputs,     potentially leading to a denial of service. Certain unusual patterns of input data can cause the common     function used to parse HTTP and MIME headers to allocate substantially more memory than required to hold     the parsed headers. An attacker can exploit this behavior to cause an HTTP server to allocate large     amounts of memory from a small request, potentially leading to memory exhaustion and a denial of service.
    With fix, header parsing now correctly allocates only the memory required to hold parsed headers.
    (CVE-2023-24534)

  - Multipart form parsing can consume large amounts of CPU and memory when processing form inputs containing     very large numbers of parts. This stems from several causes: 1. mime/multipart.Reader.ReadForm limits the     total memory a parsed multipart form can consume. ReadForm can undercount the amount of memory consumed,     leading it to accept larger inputs than intended. 2. Limiting total memory does not account for increased     pressure on the garbage collector from large numbers of small allocations in forms with many parts. 3.
    ReadForm can allocate a large number of short-lived buffers, further increasing pressure on the garbage     collector. The combination of these factors can permit an attacker to cause an program that parses     multipart forms to consume large amounts of CPU and memory, potentially resulting in a denial of service.
    This affects programs that use mime/multipart.Reader.ReadForm, as well as form parsing in the net/http     package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue. With fix,     ReadForm now does a better job of estimating the memory consumption of parsed forms, and performs many     fewer short-lived allocations. In addition, the fixed mime/multipart.Reader imposes the following limits     on the size of parsed forms: 1. Forms parsed with ReadForm may contain no more than 1000 parts. This limit     may be adjusted with the environment variable GODEBUG=multipartmaxparts=. 2. Form parts parsed with     NextPart and NextRawPart may contain no more than 10,000 header fields. In addition, forms parsed with     ReadForm may contain no more than 10,000 header fields across all parts. This limit may be adjusted with     the environment variable GODEBUG=multipartmaxheaders=. (CVE-2023-24536)

  - Calling any of the Parse functions on Go source code which contains //line directives with very large line     numbers can cause an infinite loop due to integer overflow. (CVE-2023-24537)

  - Templates do not properly consider backticks (`) as Javascript string delimiters, and do not escape them     as expected. Backticks are used, since ES6, for JS template literals. If a template contains a Go template     action within a Javascript template literal, the contents of the action can be used to terminate the     literal, injecting arbitrary Javascript code into the Go template. As ES6 template literals are rather     complex, and themselves can do string interpolation, the decision was made to simply disallow Go template     actions from being used inside of them (e.g. var a = {{.}}), since there is no obviously safe way to     allow this behavior. This takes the same approach as github.com/google/safehtml. With fix, Template.Parse     returns an Error when it encounters templates like this, with an ErrorCode of value 12. This ErrorCode is     currently unexported, but will be exported in the release of Go 1.21. Users who rely on the previous     behavior can re-enable it using the GODEBUG flag jstmpllitinterp=1, with the caveat that backticks will     now be escaped. This should be used with caution. (CVE-2023-24538)

  - 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. (CVE-2023-30861)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Red Hat Enterprise Linux CoreOS 4 host has a package installed that is affected by multiple vulnerabilities as referenced in the RHSA-2023:3541 advisory.

  - Incorrect handling of the supplementary groups in the CRI-O container engine might lead to sensitive     information disclosure or possible data modification if an attacker has direct access to the affected     container where supplementary groups are used to set access permissions and is able to execute a binary     code in that container. (CVE-2022-2995)

  - 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. (CVE-2023-30861)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Red Hat Enterprise Linux CoreOS 4 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2023:3545 advisory.

  - Not all valid JavaScript whitespace characters are considered to be whitespace. Templates containing     whitespace characters outside of the character set \t\n\f\r\u0020\u2028\u2029 in JavaScript contexts     that also contain actions may not be properly sanitized during execution. (CVE-2023-24540)

  - 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. (CVE-2023-30861)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Fedora 39 host has a package installed that is affected by a vulnerability as referenced in the FEDORA-2023-ebc3be7db1 advisory.

  - 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. (CVE-2023-30861)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The version of Oracle Business Intelligence Enterprise Edition (OAS) 6.4.0.0.0 installed on the remote host is affected by multiple vulnerabilities as referenced in the October 2023 CPU advisory, including the following:

  - Vulnerability in the Oracle Business Intelligence Enterprise Edition product of Oracle Analytics   (component: Analytics Server (Apache Spark)). The supported version that is affected is 6.4.0.0.0. Easily   exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle   Business Intelligence Enterprise Edition. While the vulnerability is in Oracle Business Intelligence   Enterprise Edition, attacks may significantly impact additional products (scope change). Successful attacks   of this vulnerability can result in takeover of Oracle Business Intelligence Enterprise Edition.
  (CVE-2023-22946)

  - Vulnerability in the Oracle Business Intelligence Enterprise Edition product of Oracle Analytics   (component: Analytics Server (Apache Hadoop)). The supported version that is affected is 6.4.0.0.0. Easily   exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle   Business Intelligence Enterprise Edition. Successful attacks of this vulnerability can result in takeover of   Oracle Business Intelligence Enterprise Edition. (CVE-2022-26612)

  - Vulnerability in the Oracle Business Intelligence Enterprise Edition product of Oracle Analytics   (component: Content Storage Service (Apache Commons Configuration)). Supported versions that are affected   are 6.4.0.0.0 and 7.0.0.0.0. Easily exploitable vulnerability allows unauthenticated attacker with network   access via HTTP to compromise Oracle Business Intelligence Enterprise Edition. Successful attacks of this   vulnerability can result in takeover of Oracle Business Intelligence Enterprise Edition. (CVE-2022-33980)   Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Debian 10 host has packages installed that are affected by a vulnerability as referenced in the dla-3536 advisory.

  - 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. (CVE-2023-30861)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote Oracle Linux 8 host has a package installed that is affected by a vulnerability as referenced in the ELSA-2023-12710 advisory.

  - 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. (CVE-2023-30861)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote openSUSE 15 host has packages installed that are affected by a vulnerability as referenced in the SUSE- SU-2023:2263-2 advisory.

  - 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. (CVE-2023-30861)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote Debian 11 host has packages installed that are affected by a vulnerability as referenced in the dsa-5442 advisory.

  - 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. (CVE-2023-30861)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

It is, therefore, affected by a vulnerability as referenced in the ALAS2023-2023-183 advisory.

  - 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. (CVE-2023-30861)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote Redhat Enterprise Linux 7 host has a package installed that is affected by a vulnerability as referenced in the RHSA-2023:3525 advisory.

  - flask: Possible disclosure of permanent session cookie due to missing Vary: Cookie header (CVE-2023-30861)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote Ubuntu 20.04 LTS / 22.04 LTS / 22.10 / 23.04 host has a package installed that is affected by a vulnerability as referenced in the USN-6111-1 advisory.

  - 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. (CVE-2023-30861)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote SUSE Linux SLED15 / SLED_SAP15 / SLES15 / SLES_SAP15 host has packages installed that are affected by a vulnerability as referenced in the SUSE-SU-2023:2264-1 advisory.

  - 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. (CVE-2023-30861)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote SUSE Linux SLED15 / SLED_SAP15 / SLES15 / SLES_SAP15 / openSUSE 15 host has packages installed that are affected by a vulnerability as referenced in the SUSE-SU-2023:2263-1 advisory.

  - 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. (CVE-2023-30861)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Severity
194323	RHEL 8 / 9 : OpenShift Container Platform 4.13.3 (RHSA-2023:3536)	Nessus	Red Hat Local Security Checks	critical
194253	RHEL 8 : OpenShift Container Platform 4.11.43 (RHSA-2023:3541)	Nessus	Red Hat Local Security Checks	high
194246	RHEL 8 : Red Hat OpenStack Platform 16.2 (python-flask) (RHSA-2023:3444)	Nessus	Red Hat Local Security Checks	high
194245	RHEL 8 : Red Hat OpenStack Platform 16.1 (python-flask) (RHSA-2023:3446)	Nessus	Red Hat Local Security Checks	high
194243	RHEL 9 : Red Hat OpenStack Platform 17.0 (python-flask) (RHSA-2023:3440)	Nessus	Red Hat Local Security Checks	high
194219	RHEL 8 / 9 : OpenShift Container Platform 4.12.21 (RHSA-2023:3545)	Nessus	Red Hat Local Security Checks	critical
189444	RHCOS 4 : OpenShift Container Platform 4.13.3 (RHSA-2023:3536)	Nessus	Red Hat Local Security Checks	critical
189413	RHCOS 4 : OpenShift Container Platform 4.11.43 (RHSA-2023:3541)	Nessus	Red Hat Local Security Checks	high
189412	RHCOS 4 : OpenShift Container Platform 4.12.21 (RHSA-2023:3545)	Nessus	Red Hat Local Security Checks	critical
185289	Fedora 39 : python-flask (2023-ebc3be7db1)	Nessus	Fedora Local Security Checks	high
183507	Oracle Business Intelligence Enterprise Edition (OAS 6.4) (October 2023 CPU)	Nessus	Misc.	critical
180017	Debian DLA-3536-1 : flask - LTS security update	Nessus	Debian Local Security Checks	high
179844	Oracle Linux 8 : python-flask (ELSA-2023-12710)	Nessus	Oracle Linux Local Security Checks	high
178692	openSUSE 15 Security Update : python-Flask (SUSE-SU-2023:2263-2)	Nessus	SuSE Local Security Checks	high
177832	Debian DSA-5442-1 : flask - security update	Nessus	Debian Local Security Checks	high
176948	Amazon Linux 2023 : python3-flask (ALAS2023-2023-183)	Nessus	Amazon Linux Local Security Checks	high
176891	RHEL 7 : python-flask (RHSA-2023:3525)	Nessus	Red Hat Local Security Checks	high
176459	Ubuntu 20.04 LTS / 22.04 LTS / 23.04 : Flask vulnerability (USN-6111-1)	Nessus	Ubuntu Local Security Checks	high
176225	SUSE SLED15 / SLES15 Security Update : python-Flask (SUSE-SU-2023:2264-1)	Nessus	SuSE Local Security Checks	high
176220	SUSE SLED15 / SLES15 / openSUSE 15 Security Update : python-Flask (SUSE-SU-2023:2263-1)	Nessus	SuSE Local Security Checks	high

Detections

Analytics

CVE-2023-30861

high

Tenable Plugins

critical

high

high

high

high

critical

critical

high

critical

high

critical

high

high

high

high

high

high

high

high

high