CVE-2022-47393
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 · uneditedAn authenticated, remote attacker may use a Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerability in multiple versions of multiple CODESYS products to force a denial-of-service situation.
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 confidenceThis is a buffer boundary vulnerability (improper restriction of operations within bounds of a memory buffer) in multiple CODESYS industrial automation products. An authenticated, remote attacker can exploit this to cause a denial-of-service condition.
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< 4.8.0.0< 4.8.0.0< 4.8.0.0< 4.8.0.0< 4.8.0.0< 4.8.0.0< 4.8.0.0< 4.8.0.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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 the CODESYS Control productDetermine which CODESYS Control variant is installed on the system. Check the product name or installed package (e.g., Codesys Control For Beaglebone Sl, Codesys Control For Linux Sl, etc.)Affected if The installed product is one of the eight affected variants listed in the CVE (Beaglebone, Empc, IoT2000, Linux, PFC100, PFC200, PLCnext, Raspberry Pi)
-
Check the installed versionLocate the installed CODESYS Control runtime version. This is typically found in the product documentation, installed package information, or runtime system information. Common locations include the runtime log files, product information dialog, or system package manager.Affected if The installed version is lower than 4.8.0.0
-
Verify remote access is enabledInspect the CODESYS runtime configuration for network communication settings. Check if the CmpSocket or network interface component is enabled and configured to accept remote connections.Affected if The runtime is configured to allow remote or network-based connections
-
Confirm authentication is in useReview the CODESYS control runtime settings and any access control configuration. Determine whether authentication is required for remote runtime communication.Affected if Remote unauthenticated access is possible (though the CVE states authenticated attacker is required, the service being exposed increases exposure)
A system is affected if it runs any of the eight listed CODESYS Control products with a version lower than 4.8.0.0 and has network connectivity enabled for the runtime interface.
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 · scoped4.8.0.0
Apply available vendor patches for affected CODESYS products, enforce least-privilege access controls, and restrict network access to authenticated interfaces.
4.8.0.0
- Identify the specific CODESYS Control product from the list: Beaglebone, Empc A/imx6, Iot2000, Linux, Pfc100, Pfc200, Plcnext, or Raspberry Pi
- Check the current installed version of the CODESYS Control product (must be < 4.8.0.0 to be vulnerable)
- Download CODESYS Control version 4.8.0.0 from the official CODESYS website (customers.codesys.com or codesys.com)
- Backup the current configuration and project files before upgrading
- Install version 4.8.0.0 of the affected CODESYS Control product
- Restart the CODESYS Control service after installation
- Verify the installed version is 4.8.0.0 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,784.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-47393 — 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-47393 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