CVE-2023-37551: CODESYS Files or Directories Accessible to External Parties in CmpApp
Noroxi assessment
Priority: Monitor (action score 26/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.49% (FIRST EPSS).
- 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.
- Fixed version: CODESYS CODESYS Control for BeagleBone SL V4.10.0.0; CODESYS CODESYS Control for emPC-A/iMX6 SL V4.10.0.0; CODESYS CODESYS Control for IOT2000 SL V4.10.0.0.
Low priority for now. Upgrade to CODESYS CODESYS Control for BeagleBone SL V4.10.0.0; CODESYS CODESYS Control for emPC-A/iMX6 SL V4.10.0.0; CODESYS CODESYS Control for IOT2000 SL V4.10.0.0 or later.
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 Codesys products in multiple versions, after successful authentication as a user, specially crafted network communication requests can utilize the CmpApp component to download files with any file extensions to the controller. In contrast to the regular file download via CmpFileTransfer, no filtering of certain file types is performed here. As a result, the integrity of the CODESYS control runtime system may be compromised by the files loaded onto the controller.
- Published
- Aug 3, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.4% · 42th percentile
- CWE
- CWE-552
Report tools
Action score
26
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 6.5
- CNA · CERTVDE
- 6.5
- 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
- A fix has been released
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 runtime system toolkit | cpe:2.3:a:codesys:control_runtime_system_toolkit |
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 slbefore 4.10.0.0
- codesys control for empc-a/imx6 slbefore 4.10.0.0
- codesys control for iot2000 slbefore 4.10.0.0
- codesys control for linux slbefore 4.10.0.0
- codesys control for pfc100 slbefore 4.10.0.0
- codesys control for pfc200 slbefore 4.10.0.0
- codesys control for plcnext slbefore 4.10.0.0
- codesys control for raspberry pi slbefore 4.10.0.0
- codesys control for wago touch panels 600 slbefore 4.10.0.0
- codesys control rte slbefore 3.5.19.20
- codesys control rte sl (for beckhoff cx)before 3.5.19.20
- codesys control runtime system toolkitbefore 3.5.19.20
- codesys control win slbefore 3.5.19.20
- codesys development systembefore 3.5.19.20
- codesys hmibefore 3.5.19.20
- codesys safety sil2before 3.5.19.20
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 CODESYS Control for BeagleBone SL
- before V4.10.0.0affected · semver
CODESYS CODESYS Control for emPC-A/iMX6 SL
- before V4.10.0.0affected · semver
CODESYS CODESYS Control for IOT2000 SL
- before V4.10.0.0affected · semver
CODESYS CODESYS Control for Linux SL
- before V4.10.0.0affected · semver
CODESYS CODESYS Control for PFC100 SL
- before V4.10.0.0affected · semver
CODESYS CODESYS Control for PFC200 SL
- before V4.10.0.0affected · semver
CODESYS CODESYS Control for PLCnext SL
- before V4.10.0.0affected · semver
CODESYS CODESYS Control for Raspberry Pi SL
- before V4.10.0.0affected · semver
CODESYS CODESYS Control for WAGO Touch Panels 600 SL
- before V4.10.0.0affected · semver
CODESYS CODESYS Control RTE (for Beckhoff CX) SL
- before V3.5.19.20affected · semver
CODESYS CODESYS Control RTE (SL)
- before V3.5.19.20affected · semver
CODESYS CODESYS Control Runtime System Toolkit
- before V3.5.19.20affected · semver
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-2023-37549Aug 3, 2023 · CODESYS: Improper Input Validation in CmpApp component26Monitor
- ← EarlierCVE-2023-37550Aug 3, 2023 · CODESYS: Improper Input Validation in CmpApp component26Monitor
- Later →CVE-2023-37552Aug 3, 2023 · CODESYS Improper Input Validation in CmpAppBP26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| CODESYS CODESYS Control for BeagleBone SL | V4.10.0.0 | Vendor (CNA) |
| CODESYS CODESYS Control for emPC-A/iMX6 SL | V4.10.0.0 | Vendor (CNA) |
| CODESYS CODESYS Control for IOT2000 SL | V4.10.0.0 | Vendor (CNA) |
| CODESYS CODESYS Control for Linux SL | V4.10.0.0 | Vendor (CNA) |
| CODESYS CODESYS Control for PFC100 SL | V4.10.0.0 | Vendor (CNA) |
| CODESYS CODESYS Control for PFC200 SL | V4.10.0.0 | Vendor (CNA) |
| CODESYS CODESYS Control for PLCnext SL | V4.10.0.0 | Vendor (CNA) |
| CODESYS CODESYS Control for Raspberry Pi SL | V4.10.0.0 | Vendor (CNA) |
| CODESYS CODESYS Control for WAGO Touch Panels 600 SL | V4.10.0.0 | Vendor (CNA) |
| CODESYS CODESYS Control RTE (for Beckhoff CX) SL | V3.5.19.20 | Vendor (CNA) |
| CODESYS CODESYS Control RTE (SL) | V3.5.19.20 | Vendor (CNA) |
| CODESYS CODESYS Control Runtime System Toolkit | V3.5.19.20 | Vendor (CNA) |
| CODESYS CODESYS Control Win (SL) | V3.5.19.20 | Vendor (CNA) |
| CODESYS CODESYS Development System V3 | V3.5.19.20 | Vendor (CNA) |
| CODESYS CODESYS HMI (SL) | V3.5.19.20 | Vendor (CNA) |
| CODESYS CODESYS Safety SIL2 Runtime Toolkit | V3.5.19.20 | Vendor (CNA) |
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.
- Vladimir Tokarev, Section 52, Azure IoT SecurityMicrosoftfinder
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
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-552 · Files or Directories Accessible to External PartiesCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
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.
Attack patterns (CAPEC)
ATT&CK techniques
- OS Credential DumpingT1003
- Data from Network Shared DriveT1039
- Automated CollectionT1119
- Data from Information RepositoriesT1213
- Data from Cloud Storage ObjectT1530
- Unsecured Credentials: Credentials in FilesT1552.001
- Unsecured Credentials: Bash HistoryT1552.003
- Unsecured Credentials: Private KeysT1552.004
- Unsecured Credentials: Group Policy PreferencesT1552.006
- Credentials from Password StoresT1555
- Data from Configuration RepositoryT1602
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.