CVE-2022-46833
What it is
Use of a Broken or Risky Cryptographic Algorithm in SICK RFU63x 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.
At a glance
- Exploitability
- Can be exploited over the network with a low-privilege account. High risk of data exposure.
- Exploit odds
- 0.3% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.3% in the next 30 days (EPSS).
- Severity: 6.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.3% · EPSS, next 30 days
- Weakness
- CWE-327 · Broken cryptographic algorithm
- Record status
- Modified
Affected
- Sick rfu630-04100 Firmware < 2.21
- Sick rfu630-04100s01 Firmware < 2.21
- Sick rfu630-04101 Firmware < 2.21
- Sick rfu630-04102 Firmware < 2.21
- Sick rfu630-04103 Firmware < 2.21
- Sick rfu630-04104 Firmware < 2.21
- Sick rfu630-04105 Firmware < 2.21
- Sick rfu630-04106 Firmware < 2.21
Attack profile CVSS 3.1 · 6.5
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2022-46833.md and follow it. Check whether this project is affected by CVE-2022-46833. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
