dbcve.org
Sim1012 0p0g200 FirmwareOperating system · Sick

CVE-2022-43990

HIGH · 7.3 CVSS v3.1 Published 2022-11-01
Fix available
A fix is available. Upgrade to 2.2.0 or later.
See remediation →
82/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
Password recovery vulnerability in SICK SIM1012 Partnumber 1098146 with firmware version <2.2.0 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 >= 2.2.0 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 SIM1012 device contains a password recovery mechanism that can be invoked by an unprivileged remote attacker to gain access to a user level called RecoverableUserLevel. This allows the attacker to escalate their privileges on the system, impacting confidentiality, integrity, and availability.

MitigationUpdate the SICK SIM1012 firmware to version 2.2.0 or later from the SICK Support Portal to address the insecure password recovery mechanism.

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
Sim1012 0p0g200 FirmwareOperating system
Affected:< 2.2.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
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

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 physical SICK SIM1012 device or access its web management interface to confirm the model number displays as SIM1012
    Affected if The device is not a SICK SIM1012 unit - this CVE only affects that specific product
  2. Check the installed firmware version
    Access the device management interface (typically via web browser or management console) and navigate to System Information or Device Status to view the firmware version number
    Affected if The firmware version is shown as 0p0g200 or any version prior to 2.2.0 (for example: 0p0g200, earlier releases)
  3. Verify remote access configuration
    Check the device network settings to determine if remote/network-based access is enabled for the password recovery feature. This may be visible in Access Control, User Management, or Security settings within the web interface
    Affected if Remote access to the password recovery mechanism is enabled and the device is network-accessible to untrusted users
  4. Confirm password recovery feature status
    Examine the user management or authentication settings in the device console to see if the RecoverableUserLevel option is present or configurable
    Affected if The RecoverableUserLevel password recovery option is available or active on the device

A user is affected if they have a SICK SIM1012 device running firmware version 0p0g200 or any version before 2.2.0 with the password recovery mechanism accessible.

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.2.0 or later
Fixed in 2.2.0
Interim mitigation

Update the SICK SIM1012 firmware to version 2.2.0 or later from the SICK Support Portal to address the insecure password recovery mechanism.

Recommended fix High confidence

Firmware version >= 2.2.0

  1. Access the SICK Support Portal at sick.com
  2. Navigate to the product page for SIM1012 (Partnumber 1098146)
  3. Locate the firmware download section
  4. Download firmware version 2.2.0 or later
  5. Follow the device's documented firmware update procedure to apply the upgrade
  6. Verify the firmware version has been successfully updated to 2.2.0 or later

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

Fix this in Sim1012 0p0g200 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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