dbcve.org
Rfu620 10100 FirmwareOperating system · Sick

CVE-2022-46832

MEDIUM · 6.5 CVSS v3.1 Published 2022-12-13
Fix available
A fix is available. Upgrade to 2.21 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
Use of a Broken or Risky Cryptographic Algorithm in SICK RFU62x firmware version < 2.21 allows a low-privileged remote attacker to decrypt the encrypted data if the user requested weak cipher suites to be used for encryption via the SSH interface. The patch and installation procedure for the firmware update is available from the responsible SICK customer contact person.

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 · moderate confidence

The SICK RFU62x firmware versions prior to 2.21 use weak or broken cryptographic algorithms for SSH encryption when users configure the device to use weak cipher suites. A low-privileged remote attacker can exploit this to decrypt sensitive data transmitted over the SSH interface.

MitigationUpdate firmware to version 2.21 or later (obtained from SICK customer contact), and ensure weak cipher suites are not enabled in the SSH configuration.

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
Rfu620 10100 FirmwareOperating system
Affected:< 2.21
Rfu620 10101 FirmwareOperating system
Affected:< 2.21
Rfu620 10102 FirmwareOperating system
Affected:< 2.21
Rfu620 10103 FirmwareOperating system
Affected:< 2.21
Rfu620 10104 FirmwareOperating system
Affected:< 2.21
Rfu620 10105 FirmwareOperating system
Affected:< 2.21
Rfu620 10107 FirmwareOperating system
Affected:< 2.21
Rfu620 10108 FirmwareOperating system
Affected:< 2.21

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

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

  1. Confirm device model is SICK RFU62x
    Access the device management interface (web UI or console) and locate the device information or system status page to verify the model is RFU620 with product codes 10100-10108.
    Affected if The device is not an RFU620 series device.
  2. Check firmware version
    Navigate to the device firmware or system information section in the management interface and record the installed firmware version number.
    Affected if The installed firmware version is less than 2.21 (for example, 2.20, 2.10, etc.).
  3. Verify SSH service is enabled
    Locate the SSH or remote access configuration settings in the device management interface and confirm whether the SSH service is turned on.
    Affected if SSH is disabled; the vulnerability only applies when SSH is actively running.
  4. Inspect SSH cipher configuration
    In the SSH or security settings configuration panel, examine the cipher suite settings or encryption algorithm options. Look for any weak or legacy cipher options (such as arcfour, aes128-cbc, 3des-cbc, or similarly deprecated algorithms).
    Affected if Weak or broken cipher suites are selected or enabled in the SSH configuration.

The environment is affected if the RFU620 firmware version is below 2.21 AND SSH is enabled AND weak cipher suites are configured in the SSH settings.

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.21 or later
Fixed in 2.21
Interim mitigation

Update firmware to version 2.21 or later (obtained from SICK customer contact), and ensure weak cipher suites are not enabled in the SSH configuration.

Recommended fix Moderate confidence

Firmware version 2.21

  1. Contact your SICK customer contact person to obtain the firmware version 2.21 update and installation procedure
  2. Download the firmware update package for your specific RFU620 model (10100, 10101, 10102, 10103, 10104, 10105, 10107, or 10108)
  3. Follow the SICK-provided installation procedure to upgrade the firmware to version 2.21
  4. After upgrading, verify that only strong cipher suites are configured for the SSH interface
  5. Ensure SSH configuration uses strong cryptographic algorithms and disable any weak or legacy cipher suites

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

Fix this in Rfu620 10100 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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