CVE-2022-22516
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe SysDrv3S driver in the CODESYS Control runtime system on Microsoft Windows allows any system user to read and write within restricted memory space.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA local privilege escalation vulnerability exists in the SysDrv3S kernel driver of the CODESYS Control runtime system on Windows. The driver fails to properly restrict memory access, allowing any local user to read and write to privileged kernel memory regions, effectively granting elevated privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 3.5.18.0< 3.5.18.0< 3.5.18.0< 3.5.18.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed CODESYS productsOpen Windows Control Panel > Programs and Features, or use PowerShell: Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like '*CODESYS*'} | Select-Object Name, VersionAffected if Any of these products appear: Codesys Control Rte Sl, Codesys Control Rte Sl (for Beckhoff Cx), Codesys Control Win Sl, or Codesys Development System
-
Verify CODESYS product versionIn Programs and Features, check the Version column for the installed CODESYS product, or right-click the installed CODESYS application > Properties > Details to view version informationAffected if The displayed version is less than 3.5.18.0 (for example, 3.5.17.10 or any version starting with 3.5.x below 3.5.18.0)
-
Check for SysDrv3S kernel driver presenceOpen Device Manager > View > Show hidden devices. Expand 'System devices' or check for a driver named 'SysDrv3S'. Alternatively, check the Windows system32/drivers folder for SysDrv3S.sys fileAffected if The SysDrv3S driver file exists on the system, particularly with a version below 3.5.18.0
-
Confirm driver version if file existsRight-click SysDrv3S.sys file > Properties > Details tab > File Version. Or use PowerShell: (Get-Item 'C:\Windows\System32\drivers\SysDrv3S.sys').VersionInfoAffected if The driver file version is present and is less than 3.5.18.0
A system is affected if it has any of the listed CODESYS products installed with a version below 3.5.18.0, and the SysDrv3S driver is present on the system.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped3.5.18.0
Apply the vendor-supplied patch for CODESYS Control to address the SysDrv3S driver vulnerability. Verify the patched driver version and confirm the runtime system functions correctly after the update.
CODESYS Control runtime version 3.5.18.0 or later
- Obtain CODESYS Control runtime version 3.5.18.0 or later from official CODESYS sources (shop.codesys.com or through your CODESYS account)
- Backup current CODESYS Control runtime configuration and projects
- Uninstall or stop the current CODESYS Control runtime services
- Install the updated CODESYS Control runtime version 3.5.18.0 or newer
- Start the CODESYS Control runtime services
- Verify the SysDrv3S driver is now properly restricted and the vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,128.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22516 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-22516 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data