CVE-2025-0289
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 · uneditedVarious Paragon Software products contain an insecure kernel resource access vulnerability facilitated by the driver not validating the MappedSystemVa pointer before passing it to HalReturnToFirmware, which can allows an attacker the ability to compromise the service.
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 confidenceThis vulnerability exists in Paragon Software kernel drivers, where the driver fails to validate the MappedSystemVa pointer before passing it to the HalReturnToFirmware function. This missing validation could allow an attacker to manipulate kernel memory pointers, potentially leading to privilege escalation or arbitrary code execution in kernel context.
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>= 15, <= 17.39>= 15, <= 16>= 15, <= 16>= 15, <= 17.39>= 4, <= 5>= 15, <= 17.39CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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.
-
Identify installed Paragon Software productsCheck Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries starting with 'Paragon' or check Program Files folder for Paragon Software directories. Alternatively, run 'Get-ItemProperty HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.Publisher -like '*Paragon*"} to list installed Paragon products.Affected if Any Paragon product from the affected list (Backup & Recovery, Disk Wiper, Drive Copy, Hard Disk Manager, Migrate OS to SSD, or Partition Manager) is found installed on the system.
-
Determine installed version of Paragon productFor each identified Paragon product, locate its version by checking the registry Uninstall entry DisplayVersion value, or check the product's main executable properties in its installation folder.Affected if The installed version falls within these affected ranges: Paragon Backup & Recovery, Hard Disk Manager, Partition Manager (version 15 through 17.39); Disk Wiper, Drive Copy (version 15 through 16); Migrate OS to SSD (version 4 through 5).
-
Check if Paragon kernel drivers are loadedOpen Command Prompt as Administrator and run 'sc query type= driver' to list all loaded drivers, then search for Paragon-related driver names (commonly starting with 'pg' or 'paragon'). Alternatively, use 'driverquery /v | findstr -i paragon' to list Paragon drivers with verbose status.Affected if Paragon kernel drivers are currently loaded in memory. The vulnerability exists in these drivers when they are active.
-
Identify vulnerable driver files on diskCheck the Windows\System32\drivers folder for Paragon kernel driver files (typically .sys files with names like pg*.sys or paragon*.sys). Use 'Get-ChildItem C:\Windows\System32\drivers | Where-Object {$_.Name -like "pg*"}' to locate them.Affected if Paragon .sys driver files exist in the System32\drivers directory. The vulnerability is present in these driver files for affected versions.
A system is affected if any Paragon Software product from the affected product list is installed with a version matching the specified ranges AND the corresponding kernel drivers are present on the system.
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 dataApply vendor-provided patches for Paragon Software products immediately. Until patches are available, consider restricting local access to systems with these products installed and monitor for suspicious driver activity.
- Consultation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0289 — 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-0289 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