dbcve.org
Icr890 4 FirmwareOperating system · Sick

CVE-2023-35698

MEDIUM · 5.3 CVSS v3.1 Published 2023-07-10
Fix available
A fix is available. Upgrade to 2.5.0 or later.
See remediation →
62/100
Remediation priority · Elevated
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
Observable Response Discrepancy in the SICK ICR890-4 could allow a remote attacker to identify valid usernames for the FTP server from the response given during a failed login attempt.

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 FTP server exhibits observable response discrepancies during authentication, returning distinguishable error messages for valid versus invalid usernames. This allows remote unauthenticated attackers to enumerate valid user accounts through repeated login attempts.

MitigationDisable the FTP server if unused, or implement rate limiting and account lockout mechanisms to prevent username enumeration. Consider migrating to SFTP or other secure transfer protocols.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 model
    Access the device web interface or check system information to confirm the model is SICK ICR890-4
    Affected if Device model is SICK ICR890-4
  2. Check firmware version
    Navigate to the device settings or system info page, or use the FTP server banner/banner grab to identify the firmware version
    Affected if Firmware version is below 2.5.0 or cannot be determined
  3. Confirm FTP server is enabled
    Check device configuration settings to verify the FTP server service is active and accessible
    Affected if FTP server is enabled and accessible on the network
  4. Test authentication response messages
    Connect to the FTP server using an invalid username first, then a valid username, and compare the error messages returned for each attempt
    Affected if Different error messages are returned for valid usernames versus invalid usernames, allowing enumeration

You are affected if the device is a SICK ICR890-4 with firmware below 2.5.0, has the FTP server enabled, and returns different error messages for valid versus invalid usernames during authentication.

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

Disable the FTP server if unused, or implement rate limiting and account lockout mechanisms to prevent username enumeration. Consider migrating to SFTP or other secure transfer protocols.

Recommended fix Moderate confidence

Firmware version 2.5.0 or later

  1. 1. Identify the current firmware version of the SICK ICR890-4 device by accessing the device's web interface or administrative console
  2. 2. Navigate to the SICK support website (sick.com) and locate the firmware download section for the ICR890-4
  3. 3. Download firmware version 2.5.0 or later from the official SICK source
  4. 4. Review the firmware upgrade instructions provided by SICK in the product documentation
  5. 5. Back up current device configuration if applicable
  6. 6. Upload and install the firmware update following the vendor's documented procedure
  7. 7. After reboot, verify the new firmware version is installed (should be 2.5.0 or higher)
  8. 8. Test the FTP login functionality to confirm the response discrepancy has been resolved

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

Fix this in Icr890 4 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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