cve.bz

CVE-2022-4224 codesys

8.8 highEPSS 0.9%

High (8.8) in codesys. EPSS 0.9% estimated probability of exploitation activity in the next 30 days.

On this page
In multiple products of CODESYS v3 in multiple versions a remote low privileged user could utilize this vulnerability to read and modify system files and OS resources or DoS the device.

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.9% (unchanged from 0.9% a week ago; 0.9% 30 days ago) estimated probability of exploitation activity in the next 30 days; 60th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-05-29. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-1188 Initialization of a Resource with an Insecure Default
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2022-4224 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-4224?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-4224?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2022-4224 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
CODESYS Control RTE (SL)from 3.0.0.0 before 3.5.19.0
CODESYS Control RTE (for Beckhoff CX) SLfrom 3.0.0.0 before 3.5.19.0
CODESYS Control Win (SL)from 3.0.0.0 before 3.5.19.0
CODESYS Runtime Toolkitfrom 3.0.0.0 before 3.5.19.0
CODESYS Safety SIL2 Runtime Toolkitfrom 3.0.0.0 before 3.5.19.0
CODESYS Safety SIL2 PSPfrom 3.0.0.0 before 3.5.19.0
CODESYS HMI (SL)from 3.0.0.0 before 3.5.19.0
CODESYS Development System V3from 3.0.0.0 before 3.5.19.0
CODESYS Control for BeagleBone SLfrom 3.0.0.0 before 4.8.0.0
CODESYS Control for emPC-A/iMX6 SLfrom 3.0.0.0 before 4.8.0.0
CODESYS Control for IOT2000 SLfrom 3.0.0.0 before 4.8.0.0
CODESYS Control for Linux SLfrom 3.0.0.0 before 4.8.0.0
CODESYS Control for PFC100 SLfrom 3.0.0.0 before 4.8.0.0
CODESYS Control for PFC200 SLfrom 3.0.0.0 before 4.8.0.0
CODESYS Control for PLCnext SLfrom 3.0.0.0 before 4.8.0.0
CODESYS Control for Raspberry Pi SLfrom 3.0.0.0 before 4.8.0.0
CODESYS Control for WAGO Touch Panels 600 SLfrom 3.0.0.0 before 4.8.0.0

ICS advisories (CISA)

AdvisoryTitlePublishedSectorsAffectedFixed
ICSA-26-076-01CODESYS in Festo Automation Suite2026-02-26Critical ManufacturingFesto Automation Suite <2.8.0.138 installed with CODESYS Development System 3.0, Festo Automation Suite <2.8.0.138 installed with CODESYS Development System 3.5.16.10, Festo Automation Suite 2.8.0.137 installed with CODESYS Development System 3.0 and 1 moreCODESYS Development System 3.5.21.20 external component of Festo Automation Suite 2.8.0.138

From CISA's ICS advisories (CSAF), provided under CISA's notification. Only the facts are shown; each advisory is on CISA's page. Credits.

Attack patterns (CAPEC)

  • CAPEC-665 Exploitation of Thunderbolt Protection Flaws Likelihood: Low · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON