dbcve.org
Id Now FirmwareOperating system · Abbott

CVE-2023-47262

MEDIUM · 5.2 CVSS v3.1 Published 2023-11-14
Fix available
A fix is available. Upgrade to 7.1 or later.
See remediation →
57/100
Remediation priority · Elevated
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
The startup process and device configurations of the Abbott ID NOW device, before v7.1, can be interrupted and/or modified via physical access to an internal serial port. Direct physical access is required to exploit.

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 · moderate confidence

The Abbott ID NOW point-of-care diagnostic device versions prior to 7.1 contain a physical security vulnerability where the device's startup process and configuration can be interrupted and modified through an exposed internal serial port. An attacker with direct physical access to the device can connect to this serial interface to tamper with device operations.

MitigationUpgrade Abbott ID NOW devices to firmware version 7.1 or later. Additionally, implement physical access controls to restrict unauthorized access to the device and its internal components.

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
Id Now FirmwareOperating system
Affected:< 7.1

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

CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L

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. Check the installed firmware version on the Abbott ID NOW device
    Access the device's system information or settings menu to view the current firmware version, or connect to the device's diagnostic interface to retrieve the firmware version number
    Affected if The displayed firmware version is below 7.1 (for example, 7.0, 6.x, or earlier)
  2. Inspect the device exterior for exposed physical interfaces
    Visually examine the device chassis and rear/underside panels for any accessible serial ports, debug connectors, or exposed circuit board headers that may be reachable without opening the device
    Affected if An exposed serial port or debug header is visible on the exterior or easily accessible without tools
  3. Examine the internal serial port connection
    If accessible, open the device enclosure (following appropriate procedures) and inspect for an exposed serial port header or connector on the main board that connects to the device's startup subsystem
    Affected if A serial port interface is present and connected to the device's boot/configuration system
  4. Verify physical access controls in the deployment environment
    Document the physical location of the device and assess whether unauthorized individuals could gain direct physical access to connect to any exposed interfaces
    Affected if The device is located in an area without restricted access or monitoring
  5. Review device configuration integrity
    If possible, compare the current device configuration against known-good baselines or verify that startup parameters remain unmodified
    Affected if Configuration settings have been altered or the device shows signs of unauthorized modification

The device is affected if it runs firmware version 7.1 or lower AND has an exposed serial port accessible for physical tampering.

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.

dbcve · scoped
Upgrade available Upgrade to 7.1 or later
Fixed in 7.1
Interim mitigation

Upgrade Abbott ID NOW devices to firmware version 7.1 or later. Additionally, implement physical access controls to restrict unauthorized access to the device and its internal components.

Recommended fix High confidence

Id Now Firmware v7.1

  1. Contact Abbott technical support or visit the official Abbott cybersecurity portal to obtain the firmware v7.1 upgrade package
  2. Follow Abbott's official firmware update procedure for the ID NOW device, which typically involves transferring the firmware via USB or network connection
  3. Ensure the device is powered on and stable during the upgrade process
  4. After upgrading, verify the firmware version displays as 7.1 or later in the device settings or startup screen
  5. Confirm that the device returns to normal operational status and all tests pass
Caveat Medical device firmware upgrades may require validation or recalibration; consult Abbott documentation for any required post-upgrade verification

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Id Now Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-47262 — 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-2023-47262 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