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.
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.
To be able to patch your environment right away, you have to make sure that you are updating first the major version to either:
August 2023
May 2023
February 2023
November 2022
We will update the blog post as new information is made available.
Thanks for the reply! I was wondering specifically, since both vulnerabilities seem to affect HTTP, if I need to upgrade given that all my proxies are configured to not allow HTTP (i.e. HTTPS only).
@Sonja_Bauernfeind Could you please try and find out if there's a firm release date scheduled for May 2023 SR5 and/or August 2023 SR2? Due to QB-20719 supposedly being fixed for those, I would prefer to patch directly to those versions.
@jeremyseipel On the question of possible workarounds as you wait for an upgrade:
An upgrade or patch is required to mitigate the vulnerability and no direct workaround is available. As per Qlik's best practices, the proxy should not be exposed to the public internet, which reduces the attack surface significantly.
All authentication methods are 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.
