CVE-2023-3273
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 Access Control in the SICK ICR890-4 could allow an unauthenticated remote attacker to affect the availability of the device by changing settings of the device such as the IP address based on missing access control.
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 confidenceImproper access control in SICK ICR890-4 devices allows unauthenticated remote attackers to change device settings including IP addresses due to missing access control checks, leading to denial of service through availability impact.
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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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 exact model is SICK ICR890-4Affected if The device is not an ICR890-4 model, then this specific CVE does not apply
-
Check the installed firmware versionLog into the device administrative interface and navigate to System > Firmware Info, or use the SICK software tools to query the device for its current firmware versionAffected if The firmware version is less than 2.5.0, indicating the device is running a vulnerable version
-
Verify administrative interface accessibilityAttempt to access the device web administrative interface from an untrusted network segment or use a port scanner to identify open HTTP/HTTPS management ports accessible from outside trusted networksAffected if The administrative web interface is reachable from untrusted networks without VPN or network segmentation, exposing the vulnerability
-
Test for authentication bypass on settingsUsing a tool like curl or a browser, attempt to access device setting change endpoints (such as IP configuration pages) directly without providing any credentialsAffected if Device settings can be modified without authentication, confirming the vulnerability is exploitable
The device is affected if it is a SICK ICR890-4 with firmware version below 2.5.0 and its administrative interface is accessible from untrusted networks without requiring authentication.
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 proper authentication for administrative functions and network segmentation to limit exposure to untrusted networks; contact SICK for firmware patches addressing the access control vulnerability.
Firmware version 2.5.0 or later
- Identify the current firmware version of the SICK ICR890-4 device
- Obtain firmware version 2.5.0 or later from the official SICK support portal (sick.com)
- Review the firmware upgrade instructions provided by SICK for the ICR890-4 device
- Apply the firmware upgrade following the vendor's documented procedure, which typically involves accessing the device management interface and uploading the new firmware file
- After upgrade, verify that the device is functioning correctly and the firmware version has been updated to 2.5.0 or later
- Confirm that the improper access control vulnerability is resolved by validating that unauthenticated users can no longer modify device settings such as IP address
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-3273 — 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-3273 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