dbcve.org
Rfu610 10600 FirmwareOperating system · Sick

CVE-2022-27581

MEDIUM · 6.5 CVSS v3.1 Published 2022-12-13
Fix available
A fix is available. Upgrade to 2.25 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 RFU61x firmware version <v2.25 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 RFU61x firmware versions prior to v2.25 implement weak cryptographic algorithms in their SSH interface. When users configure the device to use weak cipher suites, a low-privileged remote attacker can decrypt the encrypted communication. The vulnerability requires the user to have explicitly requested weak ciphers, otherwise it may not be exploitable.

MitigationUpdate firmware to v2.25 or later (contact SICK customer support for the patch) and ensure SSH configurations use strong, modern cipher suites rather than deprecated or weak algorithms.

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
Rfu610 10600 FirmwareOperating system
Affected:< 2.25
Rfu610 10601 FirmwareOperating system
Affected:< 2.25
Rfu610 10603 FirmwareOperating system
Affected:< 2.25
Rfu610 10604 FirmwareOperating system
Affected:< 2.25
Rfu610 10605 FirmwareOperating system
Affected:< 2.25
Rfu610 10607 FirmwareOperating system
Affected:< 2.25
Rfu610 10609 FirmwareOperating system
Affected:< 2.25
Rfu610 10610 FirmwareOperating system
Affected:< 2.25

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 RFU61x firmware version
    Access the device management interface or use the appropriate CLI command to retrieve the current firmware version. Common methods include logging into the web interface, using the device's diagnostics menu, or querying via SNMP or the vendor-specific management tool.
    Affected if The installed firmware version is any of the following: 10600, 10601, 10603, 10604, 10605, 10607, 10609, or 10610, and the version is prior to v2.25.
  2. Verify the exact firmware revision number
    Confirm whether the firmware revision is below v2.25. The affected versions listed include specific build numbers (10600 through 10610) that must be compared against the installed version.
    Affected if The device runs firmware version < 2.25.
  3. Examine SSH service configuration
    Locate the SSH server configuration on the RFU61x device. This is typically found in the network settings, security configuration, or SSH service parameters within the device management interface.
    Affected if The device has weak or deprecated cipher suites explicitly enabled in the SSH configuration.
  4. Review allowed cipher algorithms
    Inspect the list of allowed ciphers for the SSH service. Look for weak algorithms such as 3des-cbc, aes128-cbc, aes192-cbc, aes256-cbc, or similar deprecated cipher suites.
    Affected if Weak cipher algorithms (such as older CBC-mode ciphers or other deprecated cryptographic algorithms) are explicitly configured or allowed in the SSH settings.

The device is affected if it runs firmware version prior to 2.25 AND has weak cipher suites explicitly configured or enabled in the SSH service 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.25 or later
Fixed in 2.25
Interim mitigation

Update firmware to v2.25 or later (contact SICK customer support for the patch) and ensure SSH configurations use strong, modern cipher suites rather than deprecated or weak algorithms.

Recommended fix High confidence

Firmware version 2.25

  1. Contact your designated SICK customer contact person to request the firmware v2.25 update and installation procedure
  2. Obtain the firmware v2.25 update package from SICK
  3. Apply the firmware v2.25 update to all affected RFU610 devices following the SICK-provided installation instructions

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

Fix this in Rfu610 10600 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
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,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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