BlackTreeIndependent security intelligence
← Back to the CVE catalogue
Full vulnerability report · 2022
CVE-2022-46833High confidence

n/a SICK RFU63x Firmware — Use of a Broken or Risky Cryptographic Algorithm

n/a · SICK RFU63x Firmware

6.5MediumCVSS 3.1
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
SCA-2022-0015 · CSAF 2.0 · revision 3 · finalSICK PSIRTUse of a Broken or Risky Cryptographic Algorithm in SICK RFU6xx RADIO FREQUEN. SENSOR
26 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • SICK RFU630-04100 with Firmware <2.21
  • SICK RFU630-04100S01 with Firmware <2.21
  • SICK RFU630-04101 with Firmware <2.21
  • SICK RFU630-04102 with Firmware <2.21
  • SICK RFU630-04103 with Firmware <2.21
  • SICK RFU630-04104 with Firmware <2.21
  • SICK RFU630-04105 with Firmware <2.21
  • SICK RFU630-04106 with Firmware <2.21
  • SICK RFU630-04108 with Firmware <2.21
  • SICK RFU630-04109 with Firmware <2.21
  • SICK RFU630-04117 with Firmware <2.21
  • SICK RFU630-13100 with Firmware <2.21
Summary
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.
Remediation
The patch and installation procedure for the firmware update is available from the responsible SICK customer contact person.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2022-49615

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
01

What, why and how

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.

What

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.

Why

The product uses a broken or risky cryptographic algorithm or protocol.

How

An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The product uses a broken or risky cryptographic algorithm or protocol.

How

An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Use of a Broken or Risky Cryptographic Algorithm → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-327 ↗

CWE-327: Use of a Broken or Risky Cryptographic Algorithm. The product uses a broken or risky cryptographic algorithm or protocol.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.INoneIntegrity impact: No direct loss is represented by this metric.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkCWE-327
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
SICK RFU630-04100 with Firmware <2.21; SICK RFU630-04100S01 with Firmware <2.21; SICK RFU630-04101 with Firmware <2.21; SICK RFU630-04102 with Firmware <2.21; SICK RFU630-04103 with Firmware <2.21; SICK RFU630-04104 with Firmware <2.21; SICK RFU630-04105 with Firmware <2.21; SICK RFU630-04106 with Firmware <2.21; SICK RFU630-04108 with Firmware <2.21; SICK RFU630-04109 with Firmware <2.21; SICK RFU630-04117 with Firmware <2.21; SICK RFU630-13100 with Firmware <2.21; SICK RFU630-13100S01 with Firmware <2.21; SICK RFU630-13101 with Firmware <2.21; SICK RFU630-13102 with Firmware <2.21; SICK RFU630-13103 with Firmware <2.21; SICK RFU630-13104 with Firmware <2.21; SICK RFU630-13105 with Firmware <2.21; SICK RFU630-13106 with Firmware <2.21; SICK RFU630-13107 with Firmware <2.21; SICK RFU630-13108 with Firmware <2.21; SICK RFU630-13110 with Firmware <2.21; SICK RFU630-13111 with Firmware <2.21; SICK RFU630-13113 with Firmware <2.21; SICK RFU630-13114 with Firmware <2.21; SICK RFU630-13115 with Firmware <2.21
Fixed
SICK RFU630-04100 with Firmware 2.21; SICK RFU630-04100S01 with Firmware 2.21; SICK RFU630-04101 with Firmware 2.21; SICK RFU630-04102 with Firmware 2.21; SICK RFU630-04103 with Firmware 2.21; SICK RFU630-04104 with Firmware 2.21; SICK RFU630-04105 with Firmware 2.21; SICK RFU630-04106 with Firmware 2.21; SICK RFU630-04108 with Firmware 2.21; SICK RFU630-04109 with Firmware 2.21; SICK RFU630-04117 with Firmware 2.21; SICK RFU630-13100 with Firmware 2.21; SICK RFU630-13100S01 with Firmware 2.21; SICK RFU630-13101 with Firmware 2.21; SICK RFU630-13102 with Firmware 2.21; SICK RFU630-13103 with Firmware 2.21; SICK RFU630-13104 with Firmware 2.21; SICK RFU630-13105 with Firmware 2.21; SICK RFU630-13106 with Firmware 2.21; SICK RFU630-13107 with Firmware 2.21; SICK RFU630-13108 with Firmware 2.21; SICK RFU630-13110 with Firmware 2.21; SICK RFU630-13111 with Firmware 2.21; SICK RFU630-13113 with Firmware 2.21; SICK RFU630-13114 with Firmware 2.21; SICK RFU630-13115 with Firmware 2.21
Action
The patch and installation procedure for the firmware update is available from the responsible SICK customer contact person.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 13 Dec 2022 · Last source change 22 Apr 2025, 14:30 UTC · CWE-327 · Use of a Broken or Risky Cryptographic Algorithm

CVE recordCVE.org · 5.1
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2022-49615
Product sourceVendor CSAF · SICK PSIRT
Remediation sourceVendor CSAF · SICK PSIRT
CWE sourceCNA
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates →
  1. Vendor guidanceAuthoritative vendor guidance changed from authoritative remediation link to authoritative remediation link.
    Before
    authoritative remediation link
    After
    authoritative remediation link
    SICK PSIRT ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
ENISA EUVD · EUVD-2022-49615↗Vendor CSAF · SICK PSIRT↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2022-46833 · cve.blacktree.nl