dbcve.org
Race ConditionWeakness · CWE-362

CVE-2024-29863

HIGH · 7.8 CVSS v3.1 Published 2024-04-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
A race condition in the installer executable in Qlik Qlikview before versions May 2022 SR3 (12.70.20300) and May 2023 SR2 (12,80.20200) may allow an existing lower privileged user to cause code to be executed in the context of a Windows Administrator.

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 · moderate confidence

A race condition in the QlikView installer executable allows a local authenticated user with lower privileges to escalate to Windows Administrator context by exploiting timing vulnerabilities during the installation process.

MitigationUpgrade to QlikView May 2022 SR3 (12.70.20300) or May 2023 SR2 (12.80.20200) or later. Restrict installer execution permissions to administrators only until patching is complete.

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
Local
Complexity
High
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/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. Identify installed QlikView version
    Check the QlikView version via Windows Registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{QlikView Product ID}\DisplayVersion, or inspect the QlikView.exe file properties in the installation directory (typically C:\Program Files\QlikView\QlikView.exe)
    Affected if The installed version is earlier than 12.70.20300 or 12.80.20200, meaning it predates the fixed releases
  2. Locate QlikView installer executable
    Search for QlikView installer files such as QlikView_x64Setup.exe, QlikView_x86Setup.exe, or Setup.exe in common locations like C:\Users\<username>\Downloads, C:\Temp, or the original installer directory
    Affected if A QlikView installer executable exists on the system from an affected version
  3. Verify installer file permissions
    Right-click the installer executable, go to Properties > Security, and examine the listed users/groups with Read & Execute or Write permissions
    Affected if Non-administrator authenticated users have Write or Modify permissions to the installer directory, allowing them to influence the race condition timing
  4. Check for recent installer execution events
    Review Windows Event Viewer under Windows Logs > Security for Event ID 4688 (Process Creation) involving QlikView setup executables, noting the time and user account
    Affected if Installer execution events show the setup was run from a non-administrator account, exposing the timing vulnerability

A system is affected if QlikView version is earlier than 12.70.20300 or 12.80.20200, or if installer executables from vulnerable versions remain accessible with permissions allowing lower-privileged users to interact with them.

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 QlikView May 2022 SR3 (12.70.20300) or May 2023 SR2 (12.80.20200) or later. Restrict installer execution permissions to administrators only until patching is complete.

Recommended fix Moderate confidence

May 2022 SR3 (12.70.20300) or May 2023 SR2 (12.80.20200) depending on current version branch

  1. Identify the current QlikView version installed by checking Help > About QlikView in the client or the Programs and Features list in Windows Control Panel
  2. Determine which upgrade path applies: if currently on version 12.70.x, upgrade to May 2022 SR3 (12.70.20300); if currently on version 12.80.x, upgrade to May 2023 SR2 (12.80.20200)
  3. Obtain the appropriate installer from the official Qlik download portal or support.qlik.com after authenticating with valid Qlik account credentials
  4. Close all QlikView applications and ensure no QlikView services are running
  5. Execute the installer with appropriate permissions and follow the on-screen prompts to complete the upgrade
  6. After installation, verify the version by checking Help > About QlikView confirms the target version number
Caveat Review Qlik migration/upgrade documentation for any breaking changes between versions; test in non-production environment first

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-29863 — 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-29863 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