Arbitrary physical-memory read and write via SysDrv3S
Published Apr 7, 2022 · Updated Sep 17, 2024
Incorrect permissions in CODESYS products before 3.5.18.0 allow local users to read and write arbitrary physical memory through SysDrv3S.sys. The driver lets every system user map attacker-chosen physical addresses into the calling process without enforcing the intended memory restrictions. Exposure requires SysDrv3S.sys to have been manually selected and installed with administrative rights; installing a product setup alone does not create the affected state.
Summary
What happened
Incorrect permissions in CODESYS products before 3.5.18.0 allow local users to read and write arbitrary physical memory through SysDrv3S.sys. The driver lets every system user map attacker-chosen physical addresses into the calling process without enforcing the intended memory restrictions. Exposure requires SysDrv3S.sys to have been manually selected and installed with administrative rights; installing a product setup alone does not create the affected state.
The record
- CVE
- CVE-2022-22516
- Published
- Apr 7, 2022
- Updated
- Sep 17, 2024
- Vendor
- CODESYS GmbH
- Product
- CODESYS Control Win SL
- Classifications
- CWE-732, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 7, 2022CVE publishedPublication date reported by the CVE source.
- Sep 17, 2024Record 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=V3.5.18.0 <V3.5.18.0
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