dbcve.org
Rfu650 10100 FirmwareOperating system · Sick

CVE-2022-46834

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 RFU65x firmware version < v2.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

SICK RFU65x firmware versions prior to v2.21 use weak or broken cryptographic algorithms for SSH encryption when users configure weak cipher suites. A low-privileged remote attacker can decrypt encrypted data transmitted over SSH due to these insecure cryptographic implementations.

MitigationUpgrade SICK RFU65x firmware to version v2.21 or later, and ensure strong cipher suites are configured for SSH connections. Consult SICK customer support for the official patch and update procedure.

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
Rfu650 10100 FirmwareOperating system
Affected:< 2.21
Rfu650 10101 FirmwareOperating system
Affected:< 2.21
Rfu650 10102 FirmwareOperating system
Affected:< 2.21
Rfu650 10103 FirmwareOperating system
Affected:< 2.21
Rfu650 10104 FirmwareOperating system
Affected:< 2.21
Rfu650 10105 FirmwareOperating system
Affected:< 2.21
Rfu650 10106 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. Identify the device model
    Access the device management interface or use network discovery to confirm the device is a SICK RFU65x series unit. Check the device name or model number in the web interface, console, or SNMP inventory.
    Affected if The device is not a SICK RFU65x unit.
  2. Determine the installed firmware version
    Access the device web interface, CLI, or management console and locate the firmware version information. This is typically found under System Info, Device Status, or Firmware section.
    Affected if The firmware version is less than 2.21 (e.g., 2.20, 2.10, 1.x). Compare your version against the affected ranges: 10100, 10101, 10102, 10103, 10104, 10105, 10106 all prior to v2.21.
  3. Verify if SSH is enabled
    Check the device network services configuration. Locate the SSH service settings in the web interface or CLI under Services, Remote Access, or Security settings.
    Affected if SSH service is disabled - the vulnerability does not apply.
  4. Inspect SSH cipher suite configuration
    Examine the SSH server configuration for cipher settings. Look for options labeled Cipher, Encryption, or Key Exchange in the SSH service settings. Identify if weak or legacy cipher suites (such as aes128-cbc, 3des-cbc, or similar) are configured or allowed.
    Affected if Weak or broken cipher suites are explicitly configured or allowed in the SSH settings.

The device is affected if it is a SICK RFU65x with firmware version prior to 2.21 and has SSH enabled with weak cipher configurations.

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

Upgrade SICK RFU65x firmware to version v2.21 or later, and ensure strong cipher suites are configured for SSH connections. Consult SICK customer support for the official patch and update procedure.

Recommended fix High confidence

Rfu650 firmware v2.21

  1. Contact your SICK customer support contact person to obtain the firmware v2.21 update package
  2. Follow the standard SICK RFU65x firmware upgrade procedure (typically via the device web interface or management tool)
  3. Upload and install the v2.21 firmware to the RFU650 device
  4. Reboot the device as required by the firmware update process
  5. Verify the device is running firmware version 2.21 or higher

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

Fix this in Rfu650 10100 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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