CVE-2025-10937: Oxford Nanopore Technologies MinKNOW Improper Check for Unusual or Exceptional Conditions
Oxford Nanopore Technologies' MinKNOW software at or prior to version 24.11 creates a temporary file to store the local authentication token during startup, before copying it to its final location. This temporary file is created in a directory accessible to all users on the system. An unauthorized local user or process can exploit this behavior by placing a file lock on the temporary token file using the flock system call. This prevents MinKNOW from completing the token generation process. As a result, no valid local token is created, and the software is unable to execute commands on the sequencer. This leads to a denial-of-service (DoS) condition, blocking sequencing operations.
Affected Software
Remediation
Information
Event History
Frequently Asked Questions
What is the severity of CVE-2025-10937?
CVE-2025-10937 is classified as a medium-severity vulnerability due to its potential impact on user authentication security.
How do I fix CVE-2025-10937?
To fix CVE-2025-10937, update the MinKNOW software to a version newer than 24.11 where the issue has been addressed.
What systems are affected by CVE-2025-10937?
CVE-2025-10937 affects Oxford Nanopore Technologies' MinKNOW software versions 24.11 and earlier.
What is the nature of the vulnerability in CVE-2025-10937?
CVE-2025-10937 involves improper handling of a temporary file that stores a local authentication token, which could be accessed by unauthorized users.
Can CVE-2025-10937 lead to unauthorized access?
Yes, if exploited, CVE-2025-10937 can potentially allow unauthorized access to sensitive user authentication information.