CVE-2023-35697
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 · uneditedImproper Restriction of Excessive Authentication Attempts in the SICK ICR890-4 could allow a remote attacker to brute-force user credentials.
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 confidenceThe SICK ICR890-4 device contains an improper restriction of excessive authentication attempts vulnerability. This allows a remote attacker to perform brute-force attacks on user credentials by making repeated authentication attempts without being locked out or rate-limited.
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< 2.5.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelAccess the device web interface or check the device label/documentation to confirm the model is ICR890-4Affected if The device is not a SICK ICR890-4 model
-
Check the installed firmware versionLog into the device admin interface and navigate to System > Firmware or Status page to view the current firmware version. Compare against the affected range of < 2.5.0Affected if The firmware version displayed is below 2.5.0 (e.g., 2.4.x, 2.3.x, etc.)
-
Verify remote authentication interface accessibilityCheck if the device HTTP/HTTPS management interface is exposed to untrusted networks by reviewing firewall rules or network configurationAffected if The device authentication interface is reachable from external or untrusted networks without network segmentation
-
Confirm authentication rate limiting is not enforcedAttempt multiple failed authentication attempts (with a test account if available) or review device security settings for account lockout or rate limiting configurationAffected if The device allows unlimited authentication attempts without triggering a lockout or delay
You are affected if you have a SICK ICR890-4 device running firmware version below 2.5.0 with its authentication interface remotely accessible.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.5.0
Implement account lockout policies after a configurable number of failed login attempts, add rate limiting to authentication endpoints, and consider network segmentation to reduce attack surface exposure while awaiting vendor firmware updates.
Firmware 2.5.0 or later
- Obtain the SICK ICR890-4 firmware version 2.5.0 or later from the official SICK support website (sick.com)
- Access the device management interface for the ICR890-4
- Upload and install the firmware version 2.5.0 or later following the manufacturer's firmware upgrade instructions
- Verify the firmware was successfully installed by checking the device version information
- Confirm the brute-force protection is now properly functioning
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-35697 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-35697 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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