dbcve.org
Icr890 4 FirmwareOperating system · Sick

CVE-2023-3272

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
Cleartext Transmission of Sensitive Information in the SICK ICR890-4 could allow a remote attacker to gather sensitive information by intercepting network traffic that is not encrypted.

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 scanner transmits sensitive data in cleartext (unencrypted) across the network, enabling a remote attacker positioned on the network path to intercept and read this sensitive information through packet capture and network traffic analysis.

MitigationEnable encrypted communication protocols (TLS/SSL) for all network traffic on the device, or implement network segmentation with VPN tunneling to protect the cleartext traffic from interception.

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 the device firmware version
    Access the device management interface or check the firmware version through the device's web UI, CLI, or system information page. This is typically found under Settings > System > Firmware or a similar administrative menu path.
    Affected if The firmware version is below 2.5.0, meaning the device is running an affected version that transmits data in cleartext.
  2. Verify if encrypted network protocols are enabled
    Locate the network or communication settings within the device configuration menu. Look for options related to TLS, SSL, HTTPS, or encrypted communication. Check whether these options are enabled or disabled.
    Affected if TLS/SSL encryption for network communications is disabled or not configured, leaving traffic in cleartext.
  3. Inspect network traffic configuration
    Review the device's network security settings or communication protocol configuration. Look for fields or options that specify encryption for data transmission, such as 'Encrypt Data', 'Use SSL/TLS', or similar security protocol settings.
    Affected if The configuration shows that cleartext protocols are in use instead of encrypted alternatives.
  4. Confirm sensitive data transmission settings
    Check the data export, communication, or interface settings to determine how the device transmits captured data, credentials, or scan results. Look for settings that specify the transport method.
    Affected if The device is configured to transmit sensitive data (such as scan results, credentials, or configuration data) over unencrypted channels.

You are affected if your SICK ICR890-4 scanner is running firmware version below 2.5.0 and has network encryption (TLS/SSL) disabled or not properly configured, resulting in cleartext transmission of sensitive 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

Enable encrypted communication protocols (TLS/SSL) for all network traffic on the device, or implement network segmentation with VPN tunneling to protect the cleartext traffic from interception.

Recommended fix High confidence

Firmware version 2.5.0

  1. Obtain the SICK ICR890-4 firmware version 2.5.0 or later from the official SICK website (sick.com) or authorized distribution channels
  2. Review the SICK firmware upgrade documentation for the ICR890-4 device before proceeding
  3. Follow the standard SICK firmware update procedure for the ICR890-4, typically involving accessing the device management interface and uploading the firmware file
  4. After updating, verify that the firmware version has been successfully changed to 2.5.0 or later
  5. Confirm that network communications are now encrypted (e.g., verify HTTPS/TLS is being used for web interfaces and sensitive traffic)
Caveat Review SICK release notes for version 2.5.0 to confirm no breaking changes affect your specific use case

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
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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