dbcve.org
Icr890 4 FirmwareOperating system · Sick

CVE-2023-3270

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
Exposure of Sensitive Information to an Unauthorized Actor in the SICK ICR890-4 could allow an unauthenticated remote attacker to retrieve sensitive information about the system.

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 SICK ICR890-4 industrial scanner contains an information disclosure vulnerability allowing unauthenticated remote attackers to retrieve sensitive system information. This appears to be a classic sensitive information exposure flaw in the device's web interface, API, or network service that fails to properly restrict access to system data.

MitigationSICK has released firmware updates for the ICR890-4; organizations should apply the latest patches immediately. Additionally, network segmentation and firewall rules should restrict access to the device to trusted networks only as a defense-in-depth measure.

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. Check the installed firmware version
    Access the device's web interface or management console and navigate to System Information or About page to view the firmware version. Alternatively, use the device's API endpoint for system info if available.
    Affected if The firmware version displayed is lower than 2.5.0 (e.g., 2.4.x, 2.3.x, etc.)
  2. Verify web interface accessibility
    Attempt to access the device's web interface from an untrusted network location using a browser or HTTP client (e.g., http://[device-ip]/). Check if the login page or any system information loads without requiring credentials.
    Affected if The web interface is reachable from networks outside the trusted management VLAN without authentication being enforced first.
  3. Test for unauthenticated information disclosure
    Send HTTP requests to common API endpoints on the device (such as /api/system, /api/status, or /api/info) using a tool like curl or a browser. Observe if sensitive system data (device configuration, network settings, or diagnostic information) is returned without authentication tokens or login.
    Affected if The device returns sensitive system information or configuration data in response to unauthenticated API requests.
  4. Review network exposure of the device
    Scan the network to confirm which IP addresses and ports the device is listening on. Check if ports for the web interface (typically HTTP/HTTPS ports 80/443 or custom ports) are exposed to untrusted networks.
    Affected if The device's management web interface ports are listening on IP addresses accessible from untrusted network segments.

You are affected if the device firmware version is below 2.5.0 AND the web interface or API is accessible from an untrusted network, allowing unauthenticated retrieval of sensitive system information.

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

SICK has released firmware updates for the ICR890-4; organizations should apply the latest patches immediately. Additionally, network segmentation and firewall rules should restrict access to the device to trusted networks only as a defense-in-depth measure.

Recommended fix High confidence

ICR890-4 Firmware 2.5.0 or later

  1. Upgrade the ICR890-4 device firmware to version 2.5.0 or later.
  2. After upgrading, verify that the device is functioning correctly and that the vulnerability is remediated.
  3. Consult SICK's official firmware release notes for the ICR890-4 to confirm the fix for CVE-2023-3270 is included in the target version.

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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