dbcve.org
Paragon Backup \& RecoveryApplication · Paragon Software

CVE-2025-0285

HIGH · 7.8 CVSS v3.1 Published 2025-03-03
Fix available
A fix is available. Upgrade to after 17.39 or later.
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
Various Paragon Software products contain an arbitrary kernel memory mapping vulnerability within biontdrv.sys that is caused by a failure to properly validate the length of user supplied data, which can allow an attacker to perform privilege escalation exploits.

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

A kernel-mode driver (biontdrv.sys) in Paragon Software products fails to validate the length of user-supplied data before mapping memory, allowing an unprivileged local attacker to map arbitrary kernel memory and elevate privileges to SYSTEM level.

MitigationApply vendor-supplied patches for affected Paragon Software products to update biontdrv.sys to a patched version, or disable/uninstall the driver if not required.

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
Paragon Backup \& RecoveryApplication
Affected:>= 15, <= 17.39
Paragon Disk WiperApplication
Affected:>= 15, <= 16
Paragon Drive CopyApplication
Affected:>= 15, <= 16
Paragon Hard Disk ManagerApplication
Affected:>= 15, <= 17.39
Paragon Migrate Os To SsdApplication
Affected:>= 4, <= 5
Paragon Partition ManagerApplication
Affected:>= 15, <= 17.39

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

Work through these to decide whether this CVE applies to you.

  1. Check if any Paragon Software product is installed
    Open Control Panel > Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' in PowerShell to list installed programs. Look for Paragon Backup & Recovery, Paragon Disk Wiper, Paragon Drive Copy, Paragon Hard Disk Manager, Paragon Migrate OS to SSD, or Paragon Partition Manager.
    Affected if Any Paragon product from version 15.x up to 17.39 (or 16 for Disk Wiper/Drive Copy, or 5 for Migrate OS to SSD) is installed.
  2. Locate the biontdrv.sys driver file
    Search for biontdrv.sys on the system using File Explorer search or by running 'Get-ChildItem -Path C:\ -Filter biontdrv.sys -Recurse -ErrorAction SilentlyContinue' in PowerShell. Typical locations include C:\Windows\System32\drivers\ or the product installation directory.
    Affected if The biontdrv.sys driver file exists on the system.
  3. Check if the biontdrv.sys driver is loaded
    Open an elevated command prompt and run 'sc query biontdrv' or check the driver list via 'driverquery /v | findstr biontdrv' to see if the driver is currently loaded in memory.
    Affected if The driver is currently loaded and running (service status is RUNNING).
  4. Retrieve the driver file version
    Right-click biontdrv.sys, select Properties > Details, or run '(Get-Item "C:\Windows\System32\drivers\biontdrv.sys").VersionInfo | Format-List' in PowerShell. Note the File Version value.
    Affected if The driver file version falls within the affected ranges: 15.x through 17.39 (or 16 for Disk Wiper/Drive Copy, or 5 for Migrate OS to SSD). Compare your version against the listed affected version ranges.

A system is affected if it has any Paragon Software product (Backup & Recovery, Disk Wiper, Drive Copy, Hard Disk Manager, Migrate OS to SSD, or Partition Manager) within versions 15-17.39 (or 15-16/4-5 per product) installed AND the biontdrv.sys driver file is present, regardless of whether the driver is currently loaded.

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 a release after 17.39
Interim mitigation

Apply vendor-supplied patches for affected Paragon Software products to update biontdrv.sys to a patched version, or disable/uninstall the driver if not required.

Recommended fix Moderate confidence

Latest version of the respective Paragon product beyond version 17.39 (for Disk Wiper, Drive Copy, Hard Disk Manager, Partition Manager, Backup & Recovery) or beyond version 5 (for Migrate OS to SSD)

  1. 1. Identify the exact Paragon product and version currently installed from the list of affected products (Backup & Recovery 15-17.39, Disk Wiper 15-16, Drive Copy 15-16, Hard Disk Manager 15-17.39, Migrate OS to SSD 4-5, Partition Manager 15-17.39)
  2. 2. Visit the official Paragon Software support portal at www.paragon-software.com or their Zendesk knowledge base at paragon-software.zendesk.com to check for newer versions beyond 17.39 for Disk Wiper, Drive Copy, and Hard Disk Manager products
  3. 3. Download and install the latest version of the affected Paragon product(s)
  4. 4. Verify the biontdrv.sys driver version after upgrade matches the patched release
  5. 5. Restart the system to ensure the new driver is properly loaded
  6. 6. Confirm the vulnerability is remediated by verifying the driver properly validates input buffer lengths as expected in the patched version
Caveat Review release notes for the new version to check for any changes to disk partitioning, backup, or imaging functionality that may affect existing workflows or stored recovery points

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

Fix this in Paragon Backup \& Recovery Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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