Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-62575: CWE-732 Incorrect Permission Assignment for Critical Resource in Mirion Medical EC2 Software NMIS BioDose

0
High
VulnerabilityCVE-2025-62575cvecve-2025-62575cwe-732
Published: Tue Dec 02 2025 (12/02/2025, 21:11:20 UTC)
Source: CVE Database V5
Vendor/Project: Mirion Medical
Product: EC2 Software NMIS BioDose

Description

NMIS/BioDose V22.02 and previous versions rely on a Microsoft SQL Server database. The SQL user account 'nmdbuser' and other created accounts by default have the sysadmin role. This can lead to remote code execution through the use of certain built-in stored procedures.

AI-Powered Analysis

AILast updated: 12/02/2025, 21:17:30 UTC

Technical Analysis

CVE-2025-62575 is a vulnerability categorized under CWE-732 (Incorrect Permission Assignment for Critical Resource) affecting Mirion Medical's EC2 Software NMIS BioDose, versions 22.02 and earlier. The software relies on a Microsoft SQL Server backend where the default SQL user account 'nmdbuser' and other accounts are incorrectly assigned the sysadmin role by default. This excessive permission grants attackers the ability to execute remote code by exploiting certain built-in stored procedures within SQL Server. The vulnerability does not require user interaction or prior authentication, making it remotely exploitable over the network. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N) reflects a network attack vector with low complexity and no user interaction, requiring only limited privileges but resulting in high confidentiality and integrity impact. Although no public exploits have been reported yet, the potential for remote code execution poses a serious threat to the confidentiality, integrity, and availability of systems running this software. The vulnerability is particularly critical in healthcare environments where the software is used to manage radiation dose data, making the protection of patient data and system availability paramount. The lack of available patches at the time of disclosure necessitates immediate compensating controls to reduce risk.

Potential Impact

For European organizations, especially those in the healthcare sector using Mirion Medical's EC2 Software NMIS BioDose, this vulnerability could lead to unauthorized remote code execution on critical systems managing sensitive patient radiation dose data. This can result in data breaches compromising patient confidentiality, manipulation or deletion of critical medical data affecting treatment integrity, and potential system downtime impacting healthcare delivery. Given the regulatory environment in Europe, including GDPR and medical device regulations, exploitation could also lead to significant legal and compliance consequences. The ability to execute code remotely without user interaction or authentication increases the risk of widespread exploitation, potentially affecting multiple healthcare providers and associated supply chains. The impact extends beyond data loss to patient safety risks if medical devices or treatment planning systems are compromised.

Mitigation Recommendations

Immediate mitigation steps include auditing and reducing the privileges of all SQL Server accounts used by the NMIS BioDose software, especially removing the sysadmin role from 'nmdbuser' and any other accounts with excessive permissions. Network segmentation should be enforced to restrict access to the SQL Server instance only to trusted hosts and administrators. Implement strict monitoring and alerting for unusual database activities, such as execution of stored procedures by non-administrative users. Organizations should engage with Mirion Medical for any forthcoming patches or updates addressing this issue and plan for timely deployment. Additionally, applying SQL Server security best practices, such as using least privilege principles, disabling unused stored procedures, and enforcing strong authentication mechanisms, will help reduce risk. Backup and recovery plans should be reviewed and tested to ensure resilience against potential exploitation. Finally, conducting penetration testing and vulnerability scanning focused on this vulnerability can help identify exposure and verify mitigation effectiveness.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
icscert
Date Reserved
2025-11-11T20:56:52.854Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 692f572b3b1ed793e36e7584

Added to database: 12/2/2025, 9:16:27 PM

Last enriched: 12/2/2025, 9:17:30 PM

Last updated: 12/2/2025, 10:42:05 PM

Views: 3

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats