dbcve.org
Sim2000 FirmwareOperating system · Sick

CVE-2022-47377

CRITICAL · 9.8 CVSS v3.1 Published 2022-12-16
Fix available
A fix is available. Upgrade to 1.13.4 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Password recovery vulnerability in SICK SIM2000ST Partnumber 2086502 with firmware version <1.13.4 allows an unprivileged remote attacker to gain access to the userlevel defined as RecoverableUserLevel by invocating the password recovery mechanism method. This leads to an increase in their privileges on the system and thereby affecting the confidentiality integrity and availability of the system. An attacker can expect repeatable success by exploiting the vulnerability. The recommended solution is to update the firmware to a version >= 1.13.4 as soon as possible (available in SICK Support Portal).

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 SIM2000ST industrial device contains a password recovery vulnerability that allows an unauthenticated remote attacker to elevate privileges to the RecoverableUserLevel by exploiting the password recovery mechanism. This pre-authentication flaw affects firmware versions prior to 1.13.4 and enables complete compromise of confidentiality, integrity, and availability.

MitigationUpdate SICK SIM2000ST firmware to version 1.13.4 or higher from the SICK Support Portal immediately to remediate this critical vulnerability.

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
Sim2000 FirmwareOperating system
Affected:< 1.13.4

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Locate the device nameplate or access the device web interface/system information to confirm the model is SICK SIM2000ST or SIM2000 series
    Affected if Device is a SICK SIM2000ST or SIM2000 series unit
  2. Determine the installed firmware version
    Access the device web interface (typically via HTTP/HTTPS), navigate to System Info or About section, or use the SICK software tools to query the device for its firmware version string
    Affected if Firmware version displayed is below 1.13.4 (for example, 1.13.3, 1.12.x, 1.11.x, etc.)
  3. Check if the device web interface is accessible
    Attempt to reach the device IP address via HTTP or HTTPS from a permitted network location
    Affected if The device web interface responds and the password recovery function is available without authentication
  4. Verify password recovery is enabled
    Navigate to the password recovery or user management section of the web interface without logging in to confirm the vulnerable mechanism is exposed
    Affected if The password recovery mechanism can be accessed without prior authentication

If the device is a SICK SIM2000ST/SIM2000 with firmware version lower than 1.13.4 and the web interface is accessible, the environment is affected by this vulnerability.

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 1.13.4 or later
Fixed in 1.13.4
Interim mitigation

Update SICK SIM2000ST firmware to version 1.13.4 or higher from the SICK Support Portal immediately to remediate this critical vulnerability.

Recommended fix High confidence

Firmware version >= 1.13.4

  1. Obtain firmware version 1.13.4 or higher from the SICK Support Portal (support.sick.com)
  2. Follow SICK's documented firmware update procedure for the SIM2000ST device (Partnumber 2086502)
  3. Verify the firmware version has been successfully updated to >=1.13.4

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

Fix this in Sim2000 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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