CVE-2025-0287
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 a null pointer dereference vulnerability within biontdrv.sys that is caused by a lack of a valid MasterLrp structure in the input buffer, allowing an attacker to execute arbitrary code in the kernel, facilitating privilege escalation.
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 confidenceParagon Software kernel driver (biontdrv.sys) contains a null pointer dereference vulnerability caused by insufficient validation of the MasterLrp structure in input buffers. An attacker can exploit this to execute arbitrary code in kernel mode, achieving privilege escalation from user to SYSTEM/root 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>= 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
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 productsOpen Programs and Features (Windows) or use 'rpm -qa' / 'dpkg -l' (Linux) to list installed software. 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 of these six Paragon products are installed on the system
-
Check product version against affected rangesRight-click the installed Paragon application in Programs and Features, select Properties, and note the version. Alternatively, check the executable version in the program installation directory. Compare against: Backup & Recovery 15 to 17.39, Disk Wiper 15 to 16, Drive Copy 15 to 16, Hard Disk Manager 15 to 17.39, Migrate OS To SSD 4 to 5, Partition Manager 15 to 17.39.Affected if The installed version falls within any of these ranges
-
Locate the kernel driver biontdrv.sysSearch for biontdrv.sys in the Paragon installation directory (commonly under C:\Program Files\Paragon or C:\Program Files (x86)\Paragon). Also check system driver locations: C:\Windows\System32\driversAffected if The biontdrv.sys driver file exists on the system
-
Verify driver presence in running kernelOpen Command Prompt as Administrator and run 'sc query biontdrv' to check if the driver service exists and its state. Also run 'driverquery /v | findstr biontdrv' to list driver details.Affected if The biontdrv driver service is present and running
If any Paragon product from the list above is installed with a version in the affected range AND the biontdrv.sys driver is present (particularly if running), the system is vulnerable to CVE-2025-0287 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 dataApply available vendor patches from Paragon Software for affected products and ensure kernel driver input validation is properly implemented in future releases.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.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 $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0287 — 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-0287 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