Traffic decryption via weak SSH ciphers
Published Dec 13, 2022 · Updated Apr 22, 2025
Weak SSH cryptography in SICK RFU61x Firmware before 2.25 allows remote authenticated users to decrypt protected network traffic. The SSH service negotiates weak cipher suites requested by a client, leaving session encryption susceptible to decryption. Exploitation requires low-privileged access and a client that requests a weak suite; the bounded consequence is disclosure of transferred data.
Summary
What happened
Weak SSH cryptography in SICK RFU61x Firmware before 2.25 allows remote authenticated users to decrypt protected network traffic. The SSH service negotiates weak cipher suites requested by a client, leaving session encryption susceptible to decryption. Exploitation requires low-privileged access and a client that requests a weak suite; the bounded consequence is disclosure of transferred data.
The record
- CVE
- CVE-2022-27581
- Published
- Dec 13, 2022
- Updated
- Apr 22, 2025
- Vendor
- SICK AG
- Product
- SICK RFU61x Firmware
- Classifications
- CWE-327, T1040
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 13, 2022CVE publishedPublication date reported by the CVE source.
- Apr 22, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=<v2.25
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo