CVE-2022-46832: Use of a Broken or Risky Cryptographic Algorithm in SICK RFU62x firmware version < 2.21 allows a low-privileged remote attacker to decrypt t
Noroxi assessment
Priority: Monitor (action score 26/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.33% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Dec 13, 2022
- Updated
- Jun 17, 2026
- EPSS
- 0.3% · 26th percentile
- CWE
- CWE-327
Report tools
Action score
26
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| sick | rfu620-10107 | cpe:2.3:h:sick:rfu620-10107 |
| sick | rfu620-10100 firmware | cpe:2.3:o:sick:rfu620-10100_firmware |
| sick | rfu620-10100 | cpe:2.3:h:sick:rfu620-10100 |
| sick | rfu620-10101 firmware | cpe:2.3:o:sick:rfu620-10101_firmware |
| sick | rfu620-10101 | cpe:2.3:h:sick:rfu620-10101 |
| sick | rfu620-10102 firmware | cpe:2.3:o:sick:rfu620-10102_firmware |
| sick | rfu620-10102 | cpe:2.3:h:sick:rfu620-10102 |
| sick | rfu620-10103 firmware | cpe:2.3:o:sick:rfu620-10103_firmware |
| sick | rfu620-10103 | cpe:2.3:h:sick:rfu620-10103 |
| sick | rfu620-10104 firmware | cpe:2.3:o:sick:rfu620-10104_firmware |
| sick | rfu620-10104 | cpe:2.3:h:sick:rfu620-10104 |
| sick | rfu620-10105 firmware | cpe:2.3:o:sick:rfu620-10105_firmware |
and 30 more
Check your site's encryption
This vulnerability is about certificate validation or weak cryptography. The free SSL checker tests your certificate, enabled TLS versions and weak ciphers.
Run the SSL checkAffected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- sick rfu620-10100 firmwarebefore 2.21
- sick rfu620-10101 firmwarebefore 2.21
- sick rfu620-10102 firmwarebefore 2.21
- sick rfu620-10103 firmwarebefore 2.21
- sick rfu620-10104 firmwarebefore 2.21
- sick rfu620-10105 firmwarebefore 2.21
- sick rfu620-10107 firmwarebefore 2.21
- sick rfu620-10108 firmwarebefore 2.21
- sick rfu620-10111 firmwarebefore 2.21
- sick rfu620-10114 firmwarebefore 2.21
- sick rfu620-10118 firmwarebefore 2.21
- sick rfu620-10400 firmwarebefore 2.21
- sick rfu620-10401 firmwarebefore 2.21
- sick rfu620-10500 firmwarebefore 2.21
- sick rfu620-10501 firmwarebefore 2.21
- sick rfu620-10503 firmwarebefore 2.21
- sick rfu620-10504 firmwarebefore 2.21
- sick rfu620-10507 firmwarebefore 2.21
- sick rfu620-10508 firmwarebefore 2.21
- sick rfu620-10510 firmwarebefore 2.21
Versions reported by the vendor
Affected version ranges reported by the assigning authority (SICK AG). Independent of NVD's CPE analysis and usually ahead of it.
n/a SICK RFU62x Firmware
- <v2.21affected
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-327 · Use of a Broken or Risky Cryptographic AlgorithmCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Encryption Brute ForcingCAPEC-20likelihood: Low · Low
- Creating a Rogue Certification Authority CertificateCAPEC-459likelihood: Medium · Very High
- Signature SpoofCAPEC-473
- Signature Spoofing by Improper ValidationCAPEC-475likelihood: Low · High
- Cryptanalysis of Cellular EncryptionCAPEC-608High
- Rooting SIM CardsCAPEC-614High
- CryptanalysisCAPEC-97likelihood: Low · Very High
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.