dbcve.org
Ion Torrent Onetouch 2 FirmwareOperating system · Thermofisher

CVE-2025-54304

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
An issue was discovered on Thermo Fisher Ion Torrent OneTouch 2 INS1005527 devices. When they are powered on, an X11 display server is started. The display server listens on all network interfaces and is accessible over port 6000. The X11 access control list, by default, allows connections from 127.0.0.1 and 192.168.2.15. If a device is powered on and later connected to a network with DHCP, the device may not be assigned the 192.168.2.15 IP address, leaving the display server accessible by other devices on the network. The exposed X11 display server can then be used to gain root privileges and the ability to execute code remotely by interacting with matchbox-desktop and spawning a terminal. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.

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 confidence

The Thermo Fisher Ion Torrent OneTouch 2 device starts an X11 display server on boot that listens on all network interfaces at port 6000. The default ACL permits connections from localhost and 192.168.2.15, but when the device receives a different IP via DHCP, the ACL does not restrict access, allowing any network attacker to connect and gain root access by spawning terminals through matchbox-desktop.

MitigationIsolate the device on a dedicated VLAN with firewall rules blocking port 6000, or disable the X11 service if the device functionality permits; network segmentation is critical given the unsupported status of the device.

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
Ion Torrent Onetouch 2 FirmwareOperating system
Affected:all versions

CVSS 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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify port 6000 is exposed externally
    Scan the device from an external network host using 'nmap -p 6000 <device_ip>' or 'telnet <device_ip> 6000' to check if the X11 port is reachable
    Affected if Port 6000 is open and accepting connections from external network addresses (not just localhost)
  2. Determine device IP address
    Check the device's current IP address via DHCP lease table, router status, or by running 'ip addr' or 'ifconfig' on the device itself
    Affected if The device IP address is different from 192.168.2.15 (the only IP permitted in the default ACL)
  3. Check X11 server binding address
    On the device, run 'netstat -tlnp | grep 6000' or 'ss -tlnp | grep 6000' to see which address the X11 server is listening on
    Affected if X11 server is bound to 0.0.0.0 or an external interface IP rather than 127.0.0.1 only
  4. Verify X11 access control is permissive
    Check X11 ACL configuration by examining /etc/X11/xorg.conf or running 'xauth list' and testing remote access with 'xhost +' locally if accessible
    Affected if X11 access control allows connections from IPs other than localhost and 192.168.2.15, or ACL is not properly configured for the current DHCP-assigned IP

A user is affected if the device has an IP address different from 192.168.2.15 AND port 6000 is externally accessible, allowing unauthenticated remote X11 connections.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Isolate the device on a dedicated VLAN with firewall rules blocking port 6000, or disable the X11 service if the device functionality permits; network segmentation is critical given the unsupported status of the device.

Fix this in Ion Torrent Onetouch 2 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-54304 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-54304 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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