Edited August 30th, 15:55 CET: Added clarification on older Qlik Sense Enterprise on Windows versions Edited August 31st, 13:10 CET: Added clarification on possible workarounds (none exist) as well as information regarding what authentication methods (all) are affected and that HTTP and HTTPS are impacted Edited November 21st, 8:40 CET: Added clarification to apply the latest patches
Today, we have released five 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:
May 2023 Patch 3
February 2023 Patch 7
November 2022 Patch 10
August 2022 Patch 12
All prior versions of Qlik Sense Enterprise on Windows are affected, including releases such as May 2022, February 2022, and earlier. While no patches are currently listed for these versions, Qlik is actively investigating the possibility of patching older releases.
No workarounds can be provided. Customers should upgrade Qlik Sense Enterprise for Windows to a version containing fixes for these issues. August 2023 IR released today already contains the fix.
August 2023 Initial Release
May 2023 Patch 4
February 2023 Patch 8
November 2022 Patch 11
August 2022 Patch 13
This issue only impacts Qlik Sense Enterprise for Windows. Other Qlik products including Qlik Cloud and QlikView are NOT impacted.
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.
I managed to upgrade Qlik sense enterprise from 2021 to 2022 but now am getting an error of "backup failed" while running the PostgreSQL installer to upgrade the Repository database from version 12.5 to 14.
The logs say that the user was denied access from stopping Qlik sense repository database service. Although the user has full admin rights.
Are you running it As Administrator (so, right-click, run as admin) rather than simply with a user logged in who is admin or has the permissions? It's crucial to specifically "run as admin".
If you are and you continue to get the error, please contact support (use the Chat Now) button to begin an investigation.
Was there any official word from Qlik other than through these community pages to warn users, customers and, last of all, resellers that there was a potentially considerable security flaw in their product?
Are we seriously expected to trawl through these pages to find out if the software is safe to deploy? Or am I missing something? - I seriously hope I am.
November 2022 Patch 11 fixed CVE-2023-41266 (QB-21220) and CVE-2023-41265 (QB-21222). See the Release Notes. November 2022 Patch 12 fixed CVE-2023-48365 (QB-21683). See the Release Notes.
Patches are accumulative, so anything from patch 11 is included in patch 12.
This issue only impacts Qlik Sense Enterprise for Windows. Other Qlik products, including Qlik Cloud and QlikView (or NPrinting in your specific question), are NOT impacted.
Hi @Sonja_Bauernfeind : We are already on February 2023 Patch 10, not sure if the article is suggesting us to install Patch 8 or Do we need to upgrade to Aug 2023 IR?
If you are on February 2023 Patch 10, the you already have the security patch included. More importantly, it also includes CVE-2023-48365. There is no crucial need to upgrade to another major release.
