CVE-2022-4224: CODESYS: Exposure of Resource to Wrong Sphere in CODESYS V3
Noroxi assessment
Priority: Monitor (action score 35/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.88% (FIRST EPSS); higher than 59.1% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Mar 23, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.8% · 59th percentile
- CWE
- CWE-1188
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.8%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 8.8
- CNA · CERTVDE
- 8.8
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| codesys | control for beaglebone sl | cpe:2.3:a:codesys:control_for_beaglebone_sl |
| codesys | control for empc-a\/imx6 sl | cpe:2.3:a:codesys:control_for_empc-a\/imx6_sl |
| codesys | control for iot2000 sl | cpe:2.3:a:codesys:control_for_iot2000_sl |
| codesys | control for linux sl | cpe:2.3:a:codesys:control_for_linux_sl |
| codesys | control for pfc100 sl | cpe:2.3:a:codesys:control_for_pfc100_sl |
| codesys | control for pfc200 sl | cpe:2.3:a:codesys:control_for_pfc200_sl |
| codesys | control for plcnext sl | cpe:2.3:a:codesys:control_for_plcnext_sl |
| codesys | control for raspberry pi sl | cpe:2.3:a:codesys:control_for_raspberry_pi_sl |
| codesys | control for wago touch panels 600 sl | cpe:2.3:a:codesys:control_for_wago_touch_panels_600_sl |
| codesys | control rte sl | cpe:2.3:a:codesys:control_rte_sl |
| codesys | control rte sl \(for beckhoff cx\) | cpe:2.3:a:codesys:control_rte_sl_\(for_beckhoff_cx\) |
| codesys | control win sl | cpe:2.3:a:codesys:control_win_sl |
and 4 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- codesys control for beaglebone sl3.0 and later · before 4.8.0.0
- codesys control for empc-a/imx6 sl3.0 and later · before 4.8.0.0
- codesys control for iot2000 sl3.0 and later · before 4.8.0.0
- codesys control for linux sl3.0 and later · before 4.8.0.0
- codesys control for pfc100 sl3.0 and later · before 4.8.0.0
- codesys control for pfc200 sl3.0 and later · before 4.8.0.0
- codesys control for plcnext sl3.0 and later · before 4.8.0.0
- codesys control for raspberry pi sl3.0 and later · before 4.8.0.0
- codesys control for wago touch panels 600 sl3.0 and later · before 4.8.0.0
- codesys control rte sl3.0 and later · before 3.5.19.0
- codesys control rte sl (for beckhoff cx)3.0 and later · before 3.5.19.0
- codesys control win sl3.0 and later · before 3.5.19.0
- codesys development system3.0 and later · before 3.5.19.0
- codesys hmi sl3.0 and later · before 3.5.19.0
- codesys runtime toolkit3.0 and later · before 3.5.19.0
- codesys safety sil23.0 and later · before 3.5.19.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (CERTVDE). Independent of NVD's CPE analysis and usually ahead of it.
CODESYS Control for BeagleBone SL
- 3.0.0.0 and later · before 4.8.0.0affected
CODESYS Control for emPC-A/iMX6 SL
- 3.0.0.0 and later · before 4.8.0.0affected
CODESYS Control for IOT2000 SL
- 3.0.0.0 and later · before 4.8.0.0affected
CODESYS Control for Linux SL
- 3.0.0.0 and later · before 4.8.0.0affected
CODESYS Control for PFC100 SL
- 3.0.0.0 and later · before 4.8.0.0affected
CODESYS Control for PFC200 SL
- 3.0.0.0 and later · before 4.8.0.0affected
CODESYS Control for PLCnext SL
- 3.0.0.0 and later · before 4.8.0.0affected
CODESYS Control for Raspberry Pi SL
- 3.0.0.0 and later · before 4.8.0.0affected
CODESYS Control for WAGO Touch Panels 600 SL
- 3.0.0.0 and later · before 4.8.0.0affected
CODESYS Control RTE (for Beckhoff CX) SL
- 3.0.0.0 and later · before 3.5.19.0affected
CODESYS Control RTE (SL)
- 3.0.0.0 and later · before 3.5.19.0affected
CODESYS Control Win (SL)
- 3.0.0.0 and later · before 3.5.19.0affected
Same product
codesys: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-9010An issue was discovered in 3S-Smart CODESYS V3 products.40Plan
- CVE-2018-10612In 3S-Smart Software Solutions GmbH CODESYS Control V3 products prior to version 3.5.14.0, user access management and communication encrypti39Monitor
- CVE-2022-47379CODESYS: Multiple products prone to out-of-bounds write36Monitor
Published before and after this one in the same product
- ← EarlierCVE-2022-22518Apr 7, 2022 · A bug in the CODESYS V3 CmpUserMgr component fails to correctly apply a security policy.26Monitor
- ← EarlierCVE-2022-22519Apr 7, 2022 · Special HTTP(s) Requests can cause a buffer-read causing a crash of the webserver and the runtime system.31Monitor
- Later →CVE-2022-22508May 15, 2023 · CODESYS V3: Improper Input Validation17Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Franklin ZhaoELEX FEIGONG RESEARCH INSTITUTE of Elex CyberSecurityfinder
- Reid WightmanDigital Bondfinder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-1188 · Initialization of a Resource with an Insecure DefaultCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.