FKIE_CVE-2024-36077
Vulnerability from fkie_nvd - Published: 2024-05-22 17:16 - Updated: 2026-06-17 07:36| Vendor | Product | Version |
|---|
{
"affected": [
{
"affectedData": [
{
"product": "n/a",
"vendor": "n/a",
"versions": [
{
"status": "affected",
"version": "n/a"
}
]
}
],
"source": "cve@mitre.org"
},
{
"affectedData": [
{
"cpes": [
"cpe:2.3:a:qlik:qlik_sense:february_2024:patch_3:*:*:enterprise:windows:*:*"
],
"defaultStatus": "affected",
"product": "qlik_sense",
"vendor": "qlik",
"versions": [
{
"status": "affected",
"version": "february_2024"
}
]
},
{
"cpes": [
"cpe:2.3:a:qlik:qlik_sense:november_2023:patch_8:*:*:enterprise:windows:*:*"
],
"defaultStatus": "affected",
"product": "qlik_sense",
"vendor": "qlik",
"versions": [
{
"status": "affected",
"version": "november_2023"
}
]
},
{
"cpes": [
"cpe:2.3:a:qlik:qlik_sense:august_2023:patch_13:*:*:enterprise:windows:*:*"
],
"defaultStatus": "affected",
"product": "qlik_sense",
"vendor": "qlik",
"versions": [
{
"status": "affected",
"version": "august_2023"
}
]
},
{
"cpes": [
"cpe:2.3:a:qlik:qlik_sense:may_2023:patch_15:*:*:enterprise:windows:*:*"
],
"defaultStatus": "affected",
"product": "qlik_sense",
"vendor": "qlik",
"versions": [
{
"status": "affected",
"version": "may_2023"
}
]
},
{
"cpes": [
"cpe:2.3:a:qlik:qlik_sense:february_2023:patch_13:*:*:enterprise:windows:*:*"
],
"defaultStatus": "affected",
"product": "qlik_sense",
"vendor": "qlik",
"versions": [
{
"status": "affected",
"version": "february_2023"
}
]
},
{
"cpes": [
"cpe:2.3:a:qlik:qlik_sense:november_2022:patch_16:*:*:enterprise:windows:*:*"
],
"defaultStatus": "affected",
"product": "qlik_sense",
"vendor": "qlik",
"versions": [
{
"status": "affected",
"version": "november_2022"
}
]
},
{
"cpes": [
"cpe:2.3:a:qlik:qlik_sense:may_2022:patch_17:*:*:enterprise:windows:*:*"
],
"defaultStatus": "affected",
"product": "qlik_sense",
"vendor": "qlik",
"versions": [
{
"status": "affected",
"version": "may_2022"
}
]
}
],
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "Qlik Sense Enterprise for Windows before 14.187.4 allows a remote attacker to elevate their privilege due to improper validation. The attacker can elevate their privilege to the internal system role, which allows them to execute commands on the server. This affects February 2024 Patch 3 (14.173.3 through 14.173.7), November 2023 Patch 8 (14.159.4 through 14.159.13), August 2023 Patch 13 (14.139.3 through 14.139.20), May 2023 Patch 15 (14.129.3 through 14.129.22), February 2023 Patch 13 (14.113.1 through 14.113.18), November 2022 Patch 13 (14.97.2 through 14.97.18), August 2022 Patch 16 (14.78.3 through 14.78.23), and May 2022 Patch 17 (14.67.7 through 14.67.31). This has been fixed in May 2024 (14.187.4), February 2024 Patch 4 (14.173.8), November 2023 Patch 9 (14.159.14), August 2023 Patch 14 (14.139.21), May 2023 Patch 16 (14.129.23), February 2023 Patch 14 (14.113.19), November 2022 Patch 14 (14.97.19), August 2022 Patch 17 (14.78.25), and May 2022 Patch 18 (14.67.34)."
},
{
"lang": "es",
"value": "Qlik Sense Enterprise para Windows anterior a 14.187.4 permite a un atacante remoto elevar sus privilegios debido a una validaci\u00f3n inadecuada. El atacante puede elevar su privilegio a la funci\u00f3n interna del sistema, lo que le permite ejecutar comandos en el servidor. Esto afecta al parche 3 de febrero de 2024 (14.173.3 a 14.173.7), al parche 8 de noviembre de 2023 (14.159.4 a 14.159.13), al parche 13 de agosto de 2023 (14.139.3 a 14.139.20), al parche 15 de mayo de 2023 (14.129 .3 a 14.129.22), parche 13 de febrero de 2023 (14.113.1 a 14.113.18), parche 13 de noviembre de 2022 (14.97.2 a 14.97.18), parche 16 de agosto de 2022 (14.78.3 a 14.78.23), y el parche 17 de mayo de 2022 (del 14.67.7 al 14.67.31). Esto se solucion\u00f3 en mayo de 2024 (14.187.4), parche 4 de febrero de 2024 (14.173.8), parche 9 de noviembre de 2023 (14.159.14), parche 14 de agosto de 2023 (14.139.21), parche 16 de mayo de 2023 (14.129. 23), parche 14 de febrero de 2023 (14.113.19), parche 14 de noviembre de 2022 (14.97.19), parche 17 de agosto de 2022 (14.78.25) y parche 18 de mayo de 2022 (14.67.34)."
}
],
"id": "CVE-2024-36077",
"lastModified": "2026-06-17T07:36:05.770",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 8.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 5.9,
"source": "cve@mitre.org",
"type": "Secondary"
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2024-36077",
"options": [
{
"exploitation": "none"
},
{
"automatable": "no"
},
{
"technicalImpact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2024-05-22T17:47:43.952991Z",
"version": "2.0.3"
}
}
]
},
"published": "2024-05-22T17:16:15.377",
"references": [
{
"source": "cve@mitre.org",
"url": "https://community.qlik.com/t5/Official-Support-Articles/High-Severity-Security-fixes-for-Qlik-Sense-Enterprise-for/ta-p/2452509"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"url": "https://community.qlik.com/t5/Official-Support-Articles/High-Severity-Security-fixes-for-Qlik-Sense-Enterprise-for/ta-p/2452509"
}
],
"sourceIdentifier": "cve@mitre.org",
"vulnStatus": "Deferred",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-269"
}
],
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.