CVE-2022-4046
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 · uneditedIn CODESYS Control in multiple versions a improper restriction of operations within the bounds of a memory buffer allow an remote attacker with user privileges to gain full access of the device.
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 · moderate confidenceCODESYS Control contains a memory buffer boundary restriction flaw where operations exceed memory buffer limits. A remote attacker with existing user-level privileges can exploit this to overflow buffers and achieve full device access, compromising the PLC runtime.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 CODESYS Control runtime installationCheck for CODESYS Control process or service running on the system. On Linux-based systems, look for processes named 'CODESYSControl' or check /opt/codesys directory. On IoT2000, check /mnt/data/etc/init.d for startup scripts.Affected if CODESYS Control runtime process is running on the system
-
Confirm the specific CODESYS Control product variantInspect the installed CODESYS Control package name or binary. On BeagleBone, Raspberry Pi, or other ARM boards, check /etc/opt/codesys or the installation directory for the product-specific runtime binary.Affected if The installed product matches any of: Beaglebone SL, Empc A/imx6 SL, IoT2000 SL, Linux SL, Pfc100 SL, Pfc200 SL, Plcnext SL, or Raspberry Pi SL
-
Verify all versions are affectedCheck the installed CODESYS Control version by querying the runtime or inspecting the package. Since all versions of these products are affected, any confirmed installation of the listed variants is vulnerable.Affected if Any version of the listed CODESYS Control SL products is installed
-
Check if network exposure existsReview network configuration and firewall rules to determine if the CODESYS Control runtime is accessible over the network. CODESYS typically uses ports 1217/TCP for device communication.Affected if The CODESYS Control service is network-accessible, increasing exploitability
-
Confirm user-level access requirementThe vulnerability requires an attacker with existing user-level privileges. Verify which user accounts have access to the system and whether the CODESYS Control runtime runs with elevated privileges.Affected if The CODESYS Control runtime is running with elevated privileges and is accessible to users with lower-privilege accounts
If the system has any version of CODESYS Control SL (Beaglebone, Empc, IoT2000, Linux, Pfc100, Pfc200, Plcnext, or Raspberry Pi) installed and running, the environment is affected by this vulnerability.
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.
From vendor dataApply vendor-supplied patches for affected CODESYS Control versions, implement network segmentation to limit exposure, and enforce least-privilege access controls to reduce attack surface.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-4046 — 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-4046 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