CVE-2025-1804
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 · uneditedA vulnerability was found in Blizzard Battle.Net up to 2.39.0.15212 on Windows and classified as critical. Affected by this issue is some unknown functionality in the library profapi.dll. The manipulation leads to uncontrolled search path. The attack needs to be approached locally. The complexity of an attack is rather high. The exploitation is known to be difficult. The vendor assigns this issue a low risk level.
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 confidenceA DLL hijacking vulnerability exists in Blizzard Battle.Net's profapi.dll where the library loads DLLs from an uncontrolled search path, potentially allowing an attacker to place a malicious DLL in a location that gets loaded by the application.
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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/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.
-
Check if Blizzard Battle.Net is installedLook for Battle.Net installation in common locations: C:\Program Files (x86)\Battle.net\, C:\Program Files\Battle.net\, or check Add/Remove Programs for Battle.Net entryAffected if Battle.Net application is present on the system
-
Locate profapi.dll in Battle.Net directorySearch for profapi.dll within the Battle.Net installation folder and subdirectoriesAffected if profapi.dll exists in the Battle.Net installation directory
-
Identify the installed Battle.Net versionRight-click Battle.net.exe, select Properties, then view the Details tab for version information; or right-click the Battle.Net icon in system tray and select AboutAffected if The installed version matches or falls within an affected version range (check against vendor advisories)
-
Check for unsafe DLL search path configurationUse Process Monitor (from Sysinternals) to trace DLL loading when Battle.Net starts, looking for profapi.dll loading from locations outside the application directoryAffected if profapi.dll is loaded from a path outside the Battle.Net installation directory, indicating uncontrolled search path usage
-
Determine if Battle.Net is run from a network or removable drive locationCheck the installation path of Battle.Net: if it resides on a network share (\\server\share), mapped network drive, or removable mediaAffected if Battle.Net is installed or run from a network location, USB drive, or other untrusted path where an attacker could place a malicious DLL
A user is affected if Blizzard Battle.Net is installed with the vulnerable profapi.dll that loads from uncontrolled search paths, particularly when the application runs from network locations where an attacker could place a malicious DLL.
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 dataUsers should ensure Battle.Net is updated to the latest version and avoid running the application from untrusted network locations; the vendor must implement secure DLL loading by using full explicit paths and removing unsafe search paths.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,864.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-1804 — 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-2025-1804 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