CVE-2025-64642
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 · uneditedNMIS/BioDose V22.02 and previous versions' installation directory paths by default have insecure file permissions, which in certain deployment scenarios can enable users on client workstations to modify the program executables and libraries.
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 confidenceNMIS/BioDose V22.02 and prior versions ship with default insecure file permissions on the installation directory, allowing client workstation users to modify program executables and libraries. This can enable privilege escalation or arbitrary code execution if users replace binaries with malicious equivalents that are subsequently run by higher-privileged accounts.
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< 23.0CVSS 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 NMIS/BioDose versionLocate the version information for the installed Mirion Biodose or NMIS software. This is typically found in the program files, an about dialog, or a version file included with the installation.Affected if The installed version is V22.02 or prior, or any version prior to 23.0.
-
Locate the installation directoryFind the directory where NMIS/BioDose is installed. This is typically the program files directory or a dedicated application directory.Affected if The installation directory exists and contains executable files and libraries.
-
Check file permissions on the installation directoryInspect the access control list (ACL) or file permissions on the installation directory and its contents. On Windows, use icacls or check properties. On Unix-like systems, use ls -la to view permissions.Affected if Standard non-privileged users or the Users group have Write or Modify permissions to the installation directory or its executable/library files.
-
Verify write access for non-admin usersAttempt to verify whether a standard user account (without administrator privileges) can modify, replace, or delete executables (.exe, .dll) or library files within the installation directory.Affected if A standard user account can successfully modify or replace program executables or libraries in the installation directory.
A user is affected if the installed NMIS/BioDose version is prior to 23.0 and non-privileged users have write access to the installation directory or its executable/library files.
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.
dbcve · scoped23.0
Restrict write permissions on the installation directory to only Administrators/TrustedUsers, remove inherited weak permissions, and verify integrity of all executables and libraries after remediation.
NMIS/BioDose version 23.0 or later
- Backup the current NMIS/BioDose installation and configuration data
- Upgrade NMIS/BioDose to version 23.0 or later (the fixed release)
- After upgrade, verify that the installation directory permissions are restrictive (e.g., only administrators should have write access to program executables and libraries)
- Test that the application functions correctly after the upgrade
- Document the new file permissions configuration for compliance
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64642 — 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-64642 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