dbcve.org
Icr890 4 FirmwareOperating system · Sick

CVE-2023-3271

HIGH · 7.5 CVSS v3.1 Published 2023-07-10
Fix available
A fix is available. Upgrade to 2.5.0 or later.
See remediation →
84/100
Remediation priority · High
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
Improper Access Control in the SICK ICR890-4 could allow an unauthenticated remote attacker to gather information about the system and download data via the REST API by accessing unauthenticated endpoints.

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 SICK ICR890-4 device has REST API endpoints that are accessible without authentication, allowing unauthenticated remote attackers to gather system information and download sensitive data by directly accessing these unprotected endpoints.

MitigationImplement proper authentication and authorization checks on all REST API endpoints, or disable any endpoints that do not require unauthenticated access.

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
Icr890 4 FirmwareOperating system
Affected:< 2.5.0

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
None
Availability
None

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

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. Identify SICK ICR890-4 device on the network
    Locate the device by accessing the device web interface or checking network inventory for SICK ICR890-4 scanners. Note the IP address or hostname of the device.
    Affected if The device is a SICK ICR890-4 unit
  2. Check the installed firmware version
    Access the device web interface or administrative console and navigate to the system information or firmware version section. Alternatively, consult the device documentation for CLI commands to retrieve firmware version information.
    Affected if The firmware version is below 2.5.0 (e.g., 2.4.x, 2.3.x, etc.)
  3. Verify REST API accessibility
    Using a web browser or HTTP client (such as curl), attempt to access common REST API endpoints on the device without providing any authentication credentials. Try accessing endpoints such as /api/system, /api/info, or /api/config without login.
    Affected if HTTP responses are returned without requiring authentication, indicating unprotected API access
  4. Check for sensitive data exposure
    Without authentication, navigate to endpoints that typically expose system information, configuration files, or stored data. Document which endpoints return sensitive information without authentication prompts.
    Affected if Sensitive system information, configuration data, or files can be retrieved without any authentication

The environment is affected if the device is a SICK ICR890-4 with firmware version below 2.5.0 and its REST API endpoints are accessible without authentication, allowing exposure of system data.

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 2.5.0 or later
Fixed in 2.5.0
Interim mitigation

Implement proper authentication and authorization checks on all REST API endpoints, or disable any endpoints that do not require unauthenticated access.

Recommended fix Moderate confidence

Firmware version 2.5.0

  1. Obtain the firmware version 2.5.0 or later from the official SICK website (sick.com)
  2. Access the device administration interface for the ICR890-4
  3. Navigate to the firmware update or system maintenance section
  4. Upload the firmware file version 2.5.0 or later
  5. Apply the firmware update following the on-screen instructions
  6. After reboot, verify the device is running firmware version 2.5.0 or later
  7. Confirm that unauthenticated REST API endpoints are no longer accessible

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

Fix this in Icr890 4 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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