{"answers":{"affected":"It affects 1 product.","exploited":"Yes. Attackers have exploited CVE-2023-48365 in the wild since at least 13 Jan 2025, including in ransomware campaigns.","fix":"No fix has been published for CVE-2023-48365 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 Feb 2025.","what":"CVE-2023-48365 is a critical server-side request forgery vulnerability in n/a, published on 15 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-48365 and fix it if it is affected.\n\nWhat it is: CVE-2023-48365 is a critical server-side request forgery vulnerability in n/a, published on 15 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: Yes. Attackers have exploited CVE-2023-48365 in the wild since at least 13 Jan 2025, including in ransomware campaigns.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-48365/ (Markdown: https://insights.sbomify.com/CVE-2023-48365/index.md)","id":"CVE-2023-48365","markdown":"https://insights.sbomify.com/CVE-2023-48365/index.md","name":"CVE-2023-48365","record":{"aliases":["GHSA-2cxf-f44j-gqqf"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Qlik Sense Enterprise","requires_auth":"low_privilege","summary":"Unauthenticated attackers can execute code and escalate privileges by tunneling HTTP requests due to improper header validation in Qlik Sense Enterprise.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"qlik_sense","vendor":"qlik"}],"cvss":{"score":9.6,"severity":"critical","source":"cna","vector":"CVSS:3.1/AC:L/AV:N/A:N/C:H/I:H/PR:L/S:C/UI:N","version":"3.1"},"cwes":[{"id":"CWE-444","name":"Inconsistent Interpretation of HTTP Requests"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"exploited"},"has_fix":null,"headline":"Qlik Sense HTTP Tunneling","id":"CVE-2023-48365","indexable":true,"kev":{"dateAdded":"2025-01-13","dueDate":"2025-02-03","knownRansomwareCampaignUse":"Known","product":"Sense","requiredAction":"Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.","vendorProject":"Qlik","vulnerabilityName":"Qlik Sense HTTP Tunneling Vulnerability"},"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Race condition in Intel(R) System Security Report and System Resources Defense firmware","id":"CVE-2023-48366"},"packages":[],"prev":{"headline":"Null dereference in OpenPCS 7 V9.1","id":"CVE-2023-48364"},"products":["n/a"],"published":"2023-11-15","related":[{"cvss_score":9.6,"headline":"Qlik Sense HTTP Tunneling","id":"CVE-2023-41265","kev_date_added":"2023-12-07","published":"2023-08-29"},{"cvss_score":8.2,"headline":"Qlik Sense Path Traversal","id":"CVE-2023-41266","kev_date_added":"2023-12-07","published":"2023-08-29"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2025-61138","kev_date_added":null,"published":"2025-11-20"},{"cvss_score":5.3,"headline":"Server-side request forgery in n/a","id":"CVE-2021-36761","kev_date_added":null,"published":"2022-06-21"},{"cvss_score":5.3,"headline":"Qlik Sense Enterprise Domain User enumeration","id":"CVE-2022-0564","kev_date_added":null,"published":"2022-02-21"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"open","licence":"CC0 1.0","name":"CISA KEV"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"active","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-10-21","vendors":["n/a"]},"summary":"Unauthenticated attackers can execute code and escalate privileges by tunneling HTTP requests due to improper header validation in Qlik Sense Enterprise.","url":"https://insights.sbomify.com/CVE-2023-48365/"}