CVE-2023-1968
Illumina Nextseq 550Dx Firmware 1.0.0 – 1.3.1
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-1968 is a critical-severity Binding to an Unrestricted IP Address (CWE-1327) vulnerability in Illumina Nextseq 550Dx Firmware. Its CVSS base score is 10.0 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Steganography (T1001.002); ranked in the top 22% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-24154
Vulnerability Data
Instruments with Illumina Universal Copy Service v2.x are vulnerable due to binding to an unrestricted IP address. An unauthenticated malicious actor could use UCS to listen on all IP addresses, including those capable of accepting remote communications.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Documenting authorized network flows informs correct bind decisions and reduces the chance of 0.0.0.0 usage.
Network protection controls directly prevent exposure via unrestricted binds while fixing the weakness addresses only one vector of unauthorized access.
Configuration management enforces restricted bind addresses, covering the weakness completely but only one aspect of overall hardening.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Network security controls directly require restricting listening interfaces to specific addresses rather than 0.0.0.0.
A.8.21 requires identifying, requiring and monitoring security features (including authentication, authorization and network connection controls) from providers and formulating rules on allowed networks/services; it does not stop a product from binding to 0.0.0.0 and the weakness remains exploitable until the binding itself is changed.
Network segregation can limit the blast radius of an unrestricted binding but does not prevent the binding itself.
Secure architecture principles discourage exposing services on all interfaces, though the control is broader than this single weakness.
Secure coding guidance can catch hard-coded 0.0.0.0 bindings during development but is not the primary mitigation.