# CVE-2022-46834: Weak cryptography in SICK RFU65x Firmware

> A low-privileged remote attacker can decrypt data if weak cipher suites are enabled via SSH in SICK RFU65x firmware.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Dec 2022
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-433r-x63h-9c7r

## What is CVE-2022-46834?

CVE-2022-46834 is a medium-severity vulnerability in SICK RFU65x Firmware, published on 13 Dec 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

## Which versions are affected by CVE-2022-46834?

It affects 7 products.


Products: Sick Rfu650-10100 Firmware, Sick Rfu650-10101 Firmware, Sick Rfu650-10102 Firmware, Sick Rfu650-10103 Firmware, Sick Rfu650-10104 Firmware, Sick Rfu650-10105 Firmware, Sick Rfu650-10106 Firmware.

## How do I fix CVE-2022-46834?

No fix has been published for CVE-2022-46834 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-46834 being exploited?

There is no known exploitation of CVE-2022-46834 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-46834 and fix it if it is affected.

What it is: CVE-2022-46834 is a medium-severity vulnerability in SICK RFU65x Firmware, published on 13 Dec 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-46834 in the wild and no public exploit code.

Affected product: SICK RFU65x Firmware. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-46834/ (Markdown: https://insights.sbomify.com/CVE-2022-46834/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-46834
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-46834
- OSV: https://osv.dev/vulnerability/CVE-2022-46834

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-46834/
Summaries are generated and may contain mistakes; the official description above is the record.