Today, we have released eight service releases across the latest versions of Qlik Sense to patch the reported issues. All versions of Qlik Sense Enterprise for Windows prior to and including these releases are impacted:
August 2023 Patch 1
May 2023 Patch 5
February 2023 Patch 9
November 2022 Patch 11
August 2022 Patch 13
May 2022 Patch 15
February 2022 Patch 14
November 2021 Patch 16
No workarounds can be provided. Customers should upgrade Qlik Sense Enterprise for Windows to a version containing fixes for these issues. The listed fixes also address CV-2023-41266 and CVE-2023-41265 (link).
November 2023 IR
August 2023 Patch 2
May 2023 Patch 6
February 2023 Patch 10
November 2022 Patch 12
August 2022 Patch 14
May 2022 Patch 16
February 2022 Patch 15
November 2021 Patch 17
This issue only impacts Qlik Sense Enterprise for Windows. Other Qlik products including Qlik Cloud and QlikView are NOT impacted.
Qlik provides patches for major releases until the next Initial or Service Release is generally available. See Release Management Policy for Qlik Software. Notwithstanding, additional patches for earlier releases may be made available at Qlik’s discretion.
No mitigation can be provided. An upgrade should be performed at the earliest. As per Qlik's best practices, the proxy should not be exposed to the public internet, which reduces the attack surface significantly.
What authentication methods are affected?
All authentication methods are affected.
Are environments with HTTP disabled impacted?
Environments will be affected regardless if HTTP or HTTPS are in use. These vulnerabilities affect the HTTP protocol overall, meaning even if HTTP is disabled, the environment remains vulnerable.
These attacks don’t rely on intercepting any communication, and therefore, are indifferent whether the HTTP communication is encrypted or not.
Hello @Sonja_Bauernfeind , seems microsoft sent out an "alert" recently (again?) about this.
it may be a naive question, but apparently it is possible to "register" qlik versions/patches/security stuff (as Qlik) so that Defender can identify if an installation is at risk...
We have upgraded our Qlik Sense tool from November 2022 patch 8 to May 2023 patch 6 to avoid security vulnerabilities. but we see one of the functionality is breaking in mashup after upgrade to May 2023 patch6.
Please post about the issue you experience (including symptoms and possible error messages) in our Qlik Sense Integration forum for much better access to your peers and our support agents. We also always invite you to start a chat with us (see the Chat Now button in the bottom right corner).
Our customer point us to critical security issue after "Digital agency" published Security and Vulnerability score 8.8.
Details : CVE- 2023-5869 – Integer Overflow vulnerability could allow a user to match with a DB direct via address to memory which may cause code to run, in addition the user can read the memory
Hello @eyalnir_qlik, CVE-2023-5869 is a PostgreSQL vulnerability. To address PostgreSQL vulnerabilities, upgrade PostgreSQL. One reason why Qlik has made it easy for you to unbundle (detach) the PostgreSQL instance from Qlik Sense with QPI is that you can then seamlessly upgrade PostgreSQL (as long as your version of Qlik Sense supports the version of PostgreSQL).
Allow me a while to get back to you on this. To clarify: You mean the PostgreSQL vulnerability (CVE-2023-5869), rather than the vulnerabilities this blog post is about (CVE-2023-48365), CV-2023-41266 and CVE-2023-41265), correct?
