Skip to content
Fencer Intel
medium 6.5

CVE-2022-27581 json

Use of a Broken or Risky Cryptographic Algorithm in SICK RFU61x firmware version <v2.25 allows a low-privileged remote attacker to decrypt…

published 3y ago modified 4mo ago also EUVD-2022-32082

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 26%
public exploits
0
none known

Summary

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.

Patch / fix

  • sick rfu610-10600_firmware 2.25
  • sick rfu610-10601_firmware 2.25
  • sick rfu610-10603_firmware 2.25
  • sick rfu610-10604_firmware 2.25
  • sick rfu610-10605_firmware 2.25
  • sick rfu610-10607_firmware 2.25
  • sick rfu610-10609_firmware 2.25
  • sick rfu610-10610_firmware 2.25
  • sick rfu610-10613_firmware 2.25
  • sick rfu610-10614_firmware 2.25
  • sick rfu610-10618_firmware 2.25
  • sick rfu610-10700_firmware 2.25

Is CVE-2022-27581 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.33% chance of exploitation in the next 30 days, higher than 26% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CISA ADP 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
CNA 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Affected products

  • n/a SICK RFU61x Firmware

Classification

Weakness
  • CWE-327 Use of a Broken or Risky Cryptographic Algorithm

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.