OverwolfApplication

CVE-2024-7834

HIGH · 7.8 CVSS v3.1 Published 2024-09-04
Fix available
A fix is available. Upgrade to 250.1.1 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 local privilege escalation is caused by Overwolf loading and executing certain dynamic link library files from a user-writeable folder in SYSTEM context on launch. This allows an attacker with unprivileged access to the system to run arbitrary code with SYSTEM privileges by placing a malicious .dll file in the respective location.

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

Overwolf launches with SYSTEM privileges and loads dynamic link library files from a user-writeable folder path. An unprivileged attacker can place a malicious DLL in this location, which Overwolf will then execute in SYSTEM context, achieving privilege escalation to full system control.

MitigationApply vendor patches from Overwolf that enforce secure DLL loading from trusted locations only. Until patched, restrict or monitor write access to folders from which Overwolf loads DLLs during startup.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OverwolfApplication
Affected:< 250.1.1

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
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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. Verify Overwolf is installed
    Check for Overwolf installation by searching common paths such as Program Files and Program Files (x86), and checking registry keys under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for Overwolf entries
    Affected if Overwolf is found installed on the system
  2. Check installed version against affected range
    Locate the main Overwolf executable (typically overwolf.exe or similar) and retrieve its file version property. Compare this version number to 250.1.1
    Affected if The installed version is lower than 250.1.1 (the first digit before the decimal is the major version)
  3. Confirm Overwolf runs with SYSTEM privileges
    Check the Overwolf service configuration in Windows Services (services.msc) or examine the process token when Overwolf is running to verify it executes with SYSTEM or elevated privileges
    Affected if Overwolf runs as SYSTEM or with administrator-level privileges
  4. Identify DLL loading paths used during startup
    Use process monitoring tools (such as Process Monitor from Sysinternals) to observe which folder paths Overwolf accesses when loading dynamic link libraries during startup
    Affected if Overwolf loads DLLs from paths that standard users can write to

A system is affected if Overwolf version is below 250.1.1, runs with SYSTEM privileges, and loads DLLs from user-writeable folder paths during startup

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
Upgrade available Upgrade to 250.1.1 or later
Fixed in 250.1.1
Interim mitigation

Apply vendor patches from Overwolf that enforce secure DLL loading from trusted locations only. Until patched, restrict or monitor write access to folders from which Overwolf loads DLLs during startup.

Recommended fix Moderate confidence

250.1.1

  1. Navigate to the official Overwolf website and download the latest version of the Overwolf client
  2. Install or update to the latest available version of Overwolf
  3. Verify the installed version is 250.1.1 or higher by checking the application's About or Settings section

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

Fix this in Overwolf Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-7834 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