Device takeover via unrestricted PLC application memory
Published Aug 3, 2023 · Updated May 29, 2026
Memory-boundary violation in all versions of CODESYS Control allows remote authenticated users to gain full device access via PLC code. The Control V3 runtime fails to confine PLC application memory accesses to application data and inadequately checks application-code integrity by default. Exploitation requires authenticated PLC programmer privileges and permits crafted application code to read or write the surrounding runtime process memory.
Summary
What happened
Memory-boundary violation in all versions of CODESYS Control allows remote authenticated users to gain full device access via PLC code. The Control V3 runtime fails to confine PLC application memory accesses to application data and inadequately checks application-code integrity by default. Exploitation requires authenticated PLC programmer privileges and permits crafted application code to read or write the surrounding runtime process memory.
The record
- CVE
- CVE-2022-4046
- Published
- Aug 3, 2023
- Updated
- May 29, 2026
- Vendor
- CODESYS GmbH
- Product
- CODESYS Control Runtime System Toolkit
- Classifications
- CWE-119, T0843
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 3, 2023CVE publishedPublication date reported by the CVE source.
- May 29, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=all
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo