dbcve.org
Biodose\/nmisApplication · Mirion

CVE-2025-64298

HIGH · 7.5 CVSS v3.1 Published 2025-12-02
Fix available
A fix is available. Upgrade to 23.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
NMIS/BioDose V22.02 and previous version installations where the embedded Microsoft SQLServer Express is used are exposed in the Windows share accessed by clients in networked installs. By default, this directory has insecure directory paths that allow access to the SQL Server database and configuration files, which can contain sensitive data.

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 confidence

NMIS/BioDose V22.02 and prior versions using embedded Microsoft SQL Server Express expose database and configuration files through an insecure Windows share. The default directory paths allow unauthorized network clients to access sensitive SQL Server data files, potentially exposing credentials and confidential information.

MitigationRestrict Windows share permissions to authorized users only and secure the SQL Server data and configuration directories by applying proper NTFS access control lists (ACLs) to prevent unauthorized access to database files and configuration.

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
Biodose\/nmisApplication
Affected:< 23.0

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checks

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

  1. Identify installed Mirion Biodose/nmis version
    Check the application's version through its About dialog, installed programs list, or version file in the installation directory. Compare the version number to the affected range (V22.02 or prior, or any version < 23.0).
    Affected if The installed version is Mirion Biodose/nmis with version number less than 23.0.
  2. Confirm embedded SQL Server Express presence
    Look for Microsoft SQL Server Express installation components within the Mirion Biodose/nmis program directories, or check for SQL Server processes or services named 'SQLEXPRESS' running on the host.
    Affected if The system uses the embedded Microsoft SQL Server Express bundled with Mirion Biodose/nmis.
  3. Locate SQL Server data directories
    Identify the default data directory used by the embedded SQL Server Express. Common default paths include directories under the Mirion Biodose/nmis installation folder containing database files (.mdf, .ldf) or SQL Server configuration files.
    Affected if SQL Server data files are stored in a directory under the Mirion Biodose/nmis installation path.
  4. Check for Windows shares on SQL Server directories
    Open Command Prompt and run 'net share' to list all shared folders on the system. Identify any shares that point to or include the SQL Server data directories or Mirion Biodose/nmis configuration folders.
    Affected if A Windows share exists that exposes the directory containing SQL Server data files or configuration files.
  5. Verify share accessibility
    From a network client or using 'net view \\hostname' (substituting the actual hostname), attempt to enumerate or access the identified share to confirm it is network-accessible without authentication.
    Affected if The Windows share is accessible over the network and allows unauthorized clients to read the exposed SQL Server data files.

A system is affected if it runs Mirion Biodose/nmis version less than 23.0 with embedded SQL Server Express, and a Windows share exposes the SQL Server data or configuration directories to the network.

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 23.0 or later
Fixed in 23.0
Interim mitigation

Restrict Windows share permissions to authorized users only and secure the SQL Server data and configuration directories by applying proper NTFS access control lists (ACLs) to prevent unauthorized access to database files and configuration.

Recommended fix Moderate confidence

Version 23.0 or later

  1. 1. Backup all existing NMIS/BioDose data, database files, and configuration files before proceeding with the upgrade.
  2. 2. Review the system requirements for version 23.0 to ensure compatibility with your Windows environment.
  3. 3. Download NMIS/BioDose version 23.0 or later from the official vendor source.
  4. 4. Stop any running NMIS/BioDose services and ensure no active database connections.
  5. 5. Install version 23.0 following the vendor's documented upgrade procedure.
  6. 6. After installation, verify that the Microsoft SQL Server Express database directory and configuration files are NOT exposed through Windows share with overly permissive access.
  7. 7. Configure appropriate Windows file and share permissions on the database directories to restrict access to only authorized users and administrators.
  8. 8. Restart NMIS/BioDose services and verify the application functions correctly.
Caveat Review vendor release notes for version 23.0 to check for any breaking changes or migration requirements from previous versions

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

Fix this in Biodose\/nmis Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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