Qlik · Sense · Qlik Sense HTTP Tunneling Vulnerability
Verdict
Patch soon · actively exploited, not reachable unauthenticated from the internet, and in the top 5% of CVEs by near-term exploitation probability
Added to CISA KEV 2025-01-13 · exploited in the wild for 622 days · used in ransomware campaigns
CVSS 9.6 CRITICAL. The score is a summary; these three components are the part that decides whether something scanning the internet can use it.
| Attack vector | networkreachable over the network, with no local access needed |
|---|---|
| Privileges required | lowneeds some credentials, so a fully anonymous attacker cannot reach it directly |
| User interaction | nonecan be triggered with nobody interacting with the page or request |
| Base vector | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N |
| Weakness | CWE-444 |
This describes the vulnerability. It says nothing about whether your systems run it.
EPSS puts the probability of exploitation in the next 30 days at 0.4745, which places it in the top 5% of all tracked CVEs. The percentile is the more useful half: 0.18 in absolute terms sounds low until you know most of the internet-facing software in the world scores under that.
| EPSS probability | 0.4745 |
|---|---|
| Percentile | 0.988 — top 5% |
| Added to KEV | 2025-01-13 |
|---|---|
| Days exploited | 622 |
| Federal remediation due | not set |
| Ransomware use | known to be used in ransomware campaigns |
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Qlik Sense Enterprise for Windows before August 2023 Patch 2 allows unauthenticated remote code execution, aka QB-21683. Due to improper validation of HTTP headers, a remote attacker is able to elevate their privilege by tunneling HTTP requests, allowing them to execute HTTP requests on the backend server that hosts the repository application. The fixed versions are 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, and November 2021 Patch 17. NOTE: this issue exists because of an incomplete fix for CVE-2023-41265.