CVE-2022-47378
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 · uneditedMultiple CODESYS products in multiple versions are prone to a improper input validation vulnerability. An authenticated remote attacker may craft specific requests that use the vulnerability leading to a denial-of-service condition.
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 an improper input validation vulnerability in multiple CODESYS industrial automation products. An authenticated remote attacker can send specially crafted requests that trigger the vulnerability, causing a denial-of-service condition. The vulnerability stems from insufficient validation of input data before processing.
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 installed CODESYS Control productCheck system information, installed packages, or running services to determine which CODESYS Control variant is running (Beaglebone, Empc, IoT2000, Linux, PFC100, PFC200, PLCnext, or Raspberry Pi)Affected if A CODESYS Control product is installed but the specific variant cannot be determined
-
Determine the installed CODESYS versionLocate and inspect the CODESYS Control installation directory or check the product version through its management interface, typically found in product documentation or the control runtime propertiesAffected if The installed version is less than 4.8.0.0
-
Verify remote access services are enabledCheck if network services that allow remote connections to CODESYS are active (such as the CODESYS Runtime, web server, or API endpoints). Review system services and open network ports.Affected if Remote network services are enabled and accessible to untrusted networks without proper filtering
-
Confirm authentication is required for remote accessReview the CODESYS configuration settings to verify that authentication is enforced for remote or network-based access attempts. Check user accounts and access control settings.Affected if Remote access can be obtained without valid authentication credentials
-
Inspect input handling for the exposed interfacesIf web interface or API is exposed, examine the configuration for available input validation settings or logging that might indicate malformed request handlingAffected if The web management interface or remote API is exposed to the network without strict input validation controls
A user is affected if they are running any CODESYS Control variant (Beaglebone, Empc, IoT2000, Linux, PFC100, PFC200, PLCnext, or Raspberry Pi) with a version prior to 4.8.0.0 and have remote network access enabled with authentication.
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
Implement proper input validation and sanitization on all user-supplied data within the CODESYS products. Additionally, enforce strict authentication controls and network segmentation to limit the attack surface and restrict exploitation to legitimate authenticated users only.
CODESYS Control products (all variants) version 4.8.0.0 or later
- 1. Identify the specific CODESYS Control product in use from the affected product list (Beaglebone, Empc A/imx6, Iot2000, Linux, Pfc100, Pfc200, Plcnext, or Raspberry Pi)
- 2. Check the current installed version of the CODESYS Control product
- 3. If the current version is below 4.8.0.0, plan for an upgrade to version 4.8.0.0 or later
- 4. Before upgrading, review the product's release notes for version 4.8.0.0 to confirm the vulnerability is addressed
- 5. Perform the upgrade following the standard CODESYS product update procedure
- 6. After upgrading, verify the new version is 4.8.0.0 or higher
- 7. Test the system to ensure normal operation after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-47378 — 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-47378 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