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-54808: CWE-522 Insufficiently Protected Credentials in Oxford Nano Technologies MinKNOW

0
High
VulnerabilityCVE-2025-54808cvecve-2025-54808cwe-522
Published: Thu Oct 23 2025 (10/23/2025, 18:21:19 UTC)
Source: CVE Database V5
Vendor/Project: Oxford Nano Technologies
Product: MinKNOW

Description

Oxford Nanopore Technologies' MinKNOW software at or prior to version 24.11 stores authentication tokens in a file located in the system's temporary directory (/tmp) on the host machine. This directory is typically world-readable, allowing any local user or application to access the token. If the token is leaked (e.g., via malware infection or other local exploit), and remote access is enabled, it can be used to establish unauthorized remote connections to the sequencer. Remote access must be enabled for remote exploitation to succeed. This may occur either because the user has enabled remote access for legitimate operational reasons or because malware with elevated privileges (e.g., sudo access) enables it without user consent. This vulnerability can be chained with remote access capabilities to generate a developer token from a remote device. Developer tokens can be created with arbitrary expiration dates, enabling persistent access to the sequencer and bypassing standard authentication mechanisms.

AI-Powered Analysis

AILast updated: 10/23/2025, 18:37:51 UTC

Technical Analysis

The vulnerability CVE-2025-54808 affects Oxford Nanopore Technologies' MinKNOW software versions up to 24.11. The core issue is that authentication tokens are stored in the system's temporary directory (/tmp), which is commonly world-readable on Unix-like systems. This insecure storage violates best practices for credential protection (CWE-522). Any local user or malicious application with access to the host can read these tokens. If remote access to the sequencer is enabled, an attacker who obtains a token can remotely connect to the device without further authentication. Moreover, the attacker can leverage this access to generate developer tokens with arbitrary expiration dates, effectively creating persistent backdoors that bypass standard authentication controls. Exploitation requires local privilege level access to read the token and remote access enabled on the device. Remote access may be enabled by the user for legitimate reasons or by malware with elevated privileges. The vulnerability does not require user interaction but does require some privilege level (local) and remote access enabled. There are no known public exploits yet, but the potential for chained attacks and persistent unauthorized access makes this a significant risk. The CVSS 4.0 vector (AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N) reflects local attack vector, low complexity, partial attack complexity, partial privileges required, no user interaction, and high impact on confidentiality, integrity, and availability.

Potential Impact

For European organizations, especially those involved in genomics research, clinical diagnostics, or biotechnology using Oxford Nanopore sequencing devices, this vulnerability poses a significant risk. Unauthorized access to sequencing devices can lead to data theft, manipulation of sequencing results, or disruption of critical research and diagnostic workflows. Persistent unauthorized access via developer tokens could allow attackers to maintain long-term control over devices, potentially impacting data integrity and availability. In regulated environments, such as healthcare or research institutions under GDPR, unauthorized data access could lead to compliance violations and reputational damage. The risk is heightened in multi-user or shared computing environments where local users may have access to the host system. Additionally, if malware with elevated privileges enables remote access without user consent, the attack surface expands considerably. The lack of current patches means organizations must rely on compensating controls to reduce risk. Overall, the vulnerability threatens confidentiality, integrity, and availability of sequencing operations, which are critical in precision medicine and research.

Mitigation Recommendations

1. Immediately restrict permissions on the /tmp directory or the specific token file to prevent unauthorized local users from reading authentication tokens. Use filesystem ACLs or mount options to limit access. 2. Disable remote access to MinKNOW sequencers unless explicitly required for operational purposes. If remote access is necessary, restrict it to trusted networks and use strong network-level access controls such as VPNs or IP whitelisting. 3. Monitor logs and network traffic for unusual remote connections or token usage patterns that may indicate exploitation attempts. 4. Implement endpoint security measures to prevent malware infections that could escalate privileges or enable remote access surreptitiously. 5. Regularly audit user privileges on host machines to minimize the number of users with local access and elevated privileges. 6. Engage with Oxford Nanopore Technologies for updates and apply patches promptly once available. 7. Consider isolating sequencing devices on segmented networks to limit lateral movement in case of compromise. 8. Educate users and administrators about the risks of enabling remote access and the importance of secure credential storage. 9. Use host-based intrusion detection systems to alert on unauthorized file access or changes in remote access configurations.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
icscert
Date Reserved
2025-09-23T19:54:22.511Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 68fa73f6bf11aeb6491dbf97

Added to database: 10/23/2025, 6:29:10 PM

Last enriched: 10/23/2025, 6:37:51 PM

Last updated: 10/23/2025, 9:34:40 PM

Views: 4

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