dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2024-36077

HIGH · 8.8 CVSS v3.1 Published 2024-05-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Qlik Sense Enterprise for Windows before version 14.187.4 contains a privilege escalation vulnerability where improper input validation allows remote attackers to elevate their privileges to the internal system role, enabling arbitrary command execution on the server.

MitigationUpgrade to Qlik Sense version 14.187.4 or later, or apply the specific patch versions (14.173.8, 14.159.14, 14.139.21, 14.129.23, 14.113.19, 14.97.19, 14.78.25, or 14.67.34) corresponding to the installed release branch.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate Qlik Sense installation directory
    Check the default installation path (C:\Program Files\Qlik\Sense) or look for Qlik Sense services in Windows Services (services.msc) to identify the installation root.
    Affected if Qlik Sense Enterprise for Windows is not installed - no action needed.
  2. Identify installed Qlik Sense version
    Open Qlik Management Console (QMC) and navigate to About Qlik Sense, or check the version info in the Windows Services panel for Qlik Sense services, or examine the Version.txt file in the installation root directory.
    Affected if Unable to determine version - assume potentially vulnerable.
  3. Compare version against affected ranges
    Check if the installed version is earlier than 14.187.4. Also verify it is NOT one of the patched versions: 14.173.8, 14.159.14, 14.139.21, 14.129.23, 14.113.19, 14.97.19, 14.78.25, or 14.67.34.
    Affected if Version is below 14.187.4 and does not match any of the patched version numbers - environment is vulnerable.
  4. Verify remote access exposure
    Confirm whether the Qlik Sense web interfaces (QMC, Hub) are exposed to the network or accessible remotely, since the vulnerability allows remote privilege escalation.
    Affected if Qlik Sense is network-accessible to untrusted users - exploitation risk increases significantly.

The environment is affected if Qlik Sense Enterprise for Windows is installed with a version lower than 14.187.4 and the version does not match one of the specific patch release numbers (14.173.8, 14.159.14, 14.139.21, 14.129.23, 14.113.19, 14.97.19, 14.78.25, or 14.67.34).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Qlik Sense version 14.187.4 or later, or apply the specific patch versions (14.173.8, 14.159.14, 14.139.21, 14.129.23, 14.113.19, 14.97.19, 14.78.25, or 14.67.34) corresponding to the installed release branch.

Recommended fix High confidence

Upgrade to May 2024 (14.187.4) or the latest stable release, or apply the appropriate patch: 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), Au

  1. 1. Identify the current installed version of Qlik Sense Enterprise for Windows by checking the Qlik Management Console (QMC) or the Hub About page
  2. 2. Based on the identified version line (May 2022, August 2022, November 2022, February 2023, May 2023, August 2023, November 2023, or February 2024), determine the appropriate fixed patch version from the list provided
  3. 3. Download the corresponding security patch from Qlik's official download portal or through the Qlik Customer Success subscription
  4. 4. Schedule a maintenance window and back up the Qlik Sense repository (QSR) database and all configuration files
  5. 5. Apply the patch following Qlik's standard patch deployment procedure, typically via QMC or command line tools
  6. 6. Verify the patch was applied successfully by checking the version in the QMC About section
  7. 7. Test critical applications and workflows to ensure normal operation after the update
Caveat Standard Qlik Sense patch deployment may require service restart; test in non-production environment first to verify application compatibility

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,504.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-36077 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-36077 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data