CVE-2022-47392

CODESYS: Multiple products prone to Improper Input Validation

MEDIUM
6.5
CVSS Score
Published: May 15, 2023 at 10:01 AM UTC
Updated: June 17, 2026 at 05:13 AM UTC
17 products affected across 1 vendorControl for emPC-A/iMX6 SLControl for BeagleBone SLControl for PFC100 SL

Using CODESYS Control RTE (SL) by CODESYS?

Get instant alerts when new vulnerabilities affect CODESYS Control RTE (SL) - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM6.5
Exploit prediction
EPSS 0.9%
SSVC
No known exploit

Description

An authenticated, remote attacker may use a improper input validation vulnerability in the CmpApp/CmpAppBP/CmpAppForce Components of multiple CODESYS products in multiple versions to read from an invalid address which can lead to a denial-of-service condition.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 4.8.0.0V0.0.0.0 ≤ v < V4.8.0.00.0.0.0
Affected range stops below 4.8.0.0, so it looks safe — our inference, not a vendor statement
Affected range stops below V4.8.0.0, so it looks safe — our inference, not a vendor statement
v < 4.8.0.0V0.0.0.0 ≤ v < V4.8.0.00.0.0.0
Affected range stops below 4.8.0.0, so it looks safe — our inference, not a vendor statement
Affected range stops below V4.8.0.0, so it looks safe — our inference, not a vendor statement
v < 4.8.0.0V0.0.0.0 ≤ v < V4.8.0.00.0.0.0
Affected range stops below 4.8.0.0, so it looks safe — our inference, not a vendor statement
Affected range stops below V4.8.0.0, so it looks safe — our inference, not a vendor statement
v < 4.8.0.0V0.0.0.0 ≤ v < V4.8.0.00.0.0.0
Affected range stops below 4.8.0.0, so it looks safe — our inference, not a vendor statement
Affected range stops below V4.8.0.0, so it looks safe — our inference, not a vendor statement
v < 4.8.0.0V0.0.0.0 ≤ v < V4.8.0.00.0.0.0
Affected range stops below 4.8.0.0, so it looks safe — our inference, not a vendor statement
Affected range stops below V4.8.0.0, so it looks safe — our inference, not a vendor statement
v < 4.8.0.0V0.0.0.0 ≤ v < V4.8.0.00.0.0.0
Affected range stops below 4.8.0.0, so it looks safe — our inference, not a vendor statement
Affected range stops below V4.8.0.0, so it looks safe — our inference, not a vendor statement
v < 4.8.0.0V0.0.0.0 ≤ v < V4.8.0.00.0.0.0
Affected range stops below 4.8.0.0, so it looks safe — our inference, not a vendor statement
Affected range stops below V4.8.0.0, so it looks safe — our inference, not a vendor statement
v < 4.8.0.0V0.0.0.0 ≤ v < V4.8.0.00.0.0.0
Affected range stops below 4.8.0.0, so it looks safe — our inference, not a vendor statement
Affected range stops below V4.8.0.0, so it looks safe — our inference, not a vendor statement
v < 4.8.0.0V0.0.0.0 ≤ v < V4.8.0.00.0.0.0
Affected range stops below 4.8.0.0, so it looks safe — our inference, not a vendor statement
Affected range stops below V4.8.0.0, so it looks safe — our inference, not a vendor statement
v < 3.5.19.0V0.0.0.0 ≤ v < V3.5.19.00.0.0.0
Affected range stops below 3.5.19.0, so it looks safe — our inference, not a vendor statement
Affected range stops below V3.5.19.0, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

6.5MEDIUMCERTVDE
Attack Vector
NETWORK
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-20

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card