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.
Thanks for looking into this @Sonja_Bauernfeind . I expect there are many Qlik environments out there requiring major version upgrades if Aug 2022 is the oldest supported for the patch.
Is there anything outside of the patch that can be done as a temporary holdover until the patching/upgrades can be completed?
Do you think that this impact all the Qlik Environments irrespective of their authentication method - Windows/Forms/SAML/OIDC etc. ? or it impacts windows and Forms authentication the most.
Does it still impact if Allow HTTP is explicitly disabled on all the environments? Majority of the environments uses HTTPS only.
We have a similar question to other people - we are running the QS November 2021 version. We plan to migrate to a latest version before November 2023, but we that is not scheduled until October. We would much prefer to install a patch for the November 2021 version rather than having to bring forward the migration to a latest version of QS.
