{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-54808 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-54808 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-54808 is a high-severity vulnerability in Oxford Nanopore Technologies MinKNOW, published on 23 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-54808 and fix it if it is affected.\n\nWhat it is: CVE-2025-54808 is a high-severity vulnerability in Oxford Nanopore Technologies MinKNOW, published on 23 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-54808 in the wild and no public exploit code.\n\nAffected product: Oxford Nanopore Technologies MinKNOW. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-54808/ (Markdown: https://insights.sbomify.com/CVE-2025-54808/index.md)","id":"CVE-2025-54808","markdown":"https://insights.sbomify.com/CVE-2025-54808/index.md","name":"CVE-2025-54808","record":{"aliases":["GHSA-7p36-wh9x-8c9p"],"analysis":{"component_type":"ics_ot","fix_type":"upgrade","impacts":["privilege_escalation","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"DNA sequencer software","requires_auth":"low_privilege","summary":"Local attackers can steal authentication tokens from world-readable temp files to gain unauthorized remote access to DNA sequencers if remote access is enabled.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"icscert","cpe":[],"cvss":{"score":7.3,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-522","name":"Insufficiently Protected Credentials"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Oxford Nanopore Technologies MinKNOW Insufficiently Protected Credentials","id":"CVE-2025-54808","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"F5 Access for Android vulnerability","id":"CVE-2025-54809"},"packages":[],"prev":{"headline":"Dover Fueling Solutions ProGauge MagLink LX 4 Devices Use of Hard-coded Cryptographic Key","id":"CVE-2025-54807"},"products":["MinKNOW"],"published":"2025-10-23","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-06-04","vendors":["Oxford Nanopore Technologies"]},"summary":"Local attackers can steal authentication tokens from world-readable temp files to gain unauthorized remote access to DNA sequencers if remote access is enabled.","url":"https://insights.sbomify.com/CVE-2025-54808/"}