CVE-2020-15932
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 · uneditedOverwolf before 0.149.2.30 mishandles Symbolic Links during updates, causing elevation of privileges.
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 confidenceOverwolf before version 0.149.2.30 contains a privilege escalation vulnerability in its update mechanism due to improper handling of symbolic links. During the update process, the application fails to properly validate or sanitize symbolic links, allowing an attacker to potentially manipulate file system operations and gain elevated privileges.
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< 0.149.2.30CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Locate Overwolf installation directoryCheck common installation paths such as Program Files\Overwolf or look for Overwolf in the list of installed applications via Windows Settings or Registry (HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall)Affected if Overwolf is found installed on the system
-
Find the main Overwolf executable or DLL containing version informationBrowse the Overwolf installation folder and identify the primary executable (commonly overwolf.exe or a versioned DLL). Right-click the file, select Properties, and view the Details tab for version information.Affected if A versioned Overwolf executable or DLL exists in the installation directory
-
Extract the installed version numberRead the File Version or Product Version field from the executable's properties, or use command line: powershell "(Get-Item 'C:\Path\To\overwolf.exe').VersionInfo.FileVersion" (adjust path to actual location)Affected if A version number is successfully retrieved from the Overwolf binary
-
Compare version against the fixed releaseCompare the extracted version to 0.149.2.30 using version comparison (e.g., 0.149.2.30 is the first safe version; anything below such as 0.149.2.0, 0.148.x, etc. is affected)Affected if The installed version is lower than 0.149.2.30 (e.g., 0.149.2.0, 0.148.0, or any earlier release)
If Overwolf is installed and the version is below 0.149.2.30, the update mechanism is vulnerable to symbolic link exploitation and privilege escalation.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data0.149.2.30
Upgrade Overwolf to version 0.149.2.30 or later to remediate this vulnerability. Organizations should prioritize updating affected installations given the high CVSS score and the privilege escalation nature of the flaw.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-15932 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-15932 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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