CVE-2023-48365
Qlik Sense august_2022 … november_2022
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:NSummary
CVE-2023-48365 is a critical-severity HTTP Request/Response Smuggling (CWE-444) vulnerability in Qlik Qlik Sense. Its CVSS base score is 9.6 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 2% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
Qlik Sense Enterprise for Windows versions prior to the August 2023 Patch 2 are affected by CVE-2023-48365, a high-severity flaw that permits unauthenticated remote code execution. The root cause is improper validation of HTTP headers that allows request tunneling, and the issue stems from an incomplete remediation of the earlier CVE-2023-41265. The vulnerability carries a CVSS score of 9.6 and is tracked under CWE-444.
An attacker with network access can exploit the header-validation weakness to elevate privileges and forward arbitrary HTTP requests to the backend repository server, achieving remote code execution on that host without requiring authentication.
Vendor guidance published by Qlik directs customers to apply one of the listed fixed releases, specifically August 2023 Patch 2 or the corresponding back-ported patches for earlier branches. The flaw is also catalogued in CISA’s Known Exploited Vulnerabilities list, confirming in-the-wild exploitation.
The associated EPSS score has reached a peak of 0.6423 with a current value of 0.5622, indicating sustained exploitation interest after disclosure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-52419
Vulnerability Data
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…
more
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.
- CWE(s)
- KEV Date Added
- 13 January 2025
Related Threats
Threat-Actor AttributionAI
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V4.1.3V4.2.4V1.5.3V4.1.1
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Configuration management can enforce uniform HTTP parsing rules across intermediaries, directly mitigating inconsistent interpretation.
Network monitoring can detect smuggling attempts via anomalous HTTP traffic or logs, while eliminating the inconsistency directly aids detection of such events.
Network protections can enforce consistent HTTP proxy/firewall behavior to block smuggling, and removing the weakness helps prevent unauthorized access via request smuggling.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect HTTP request smuggling vulnerabilities in intermediary components.
Network security controls can enforce consistent HTTP parsing and proxy behavior that mitigates request smuggling.
Secure network services include hardening proxies and gateways against inconsistent HTTP interpretation.
Secure SDLC practices require threat modeling and testing for HTTP parsing inconsistencies in intermediaries.
Application security requirements can mandate strict HTTP message validation and canonicalization.
Secure architecture principles include consistent protocol handling and defense-in-depth for proxies.