CVE-2022-47391
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 multiple CODESYS products in multiple versions an unauthorized, remote attacker may use a improper input validation vulnerability to read from invalid addresses leading to a denial of service.
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 products that allows unauthorized remote attackers to read from invalid memory addresses, causing 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 installed CODESYS productCheck the installed CODESYS Control runtime on the system. Common locations: /etc/codesys, /opt/codesys, or check installed packages via system package manager. Look for product name in installed files or runtime documentation.Affected if The product matches one of: Codesys Control For Beaglebone, Empc A/imx6, Iot2000, Linux, Pfc100, Pfc200, Plcnext, or Raspberry Pi SL variants.
-
Check CODESYS runtime versionRun the CODESYS runtime with version flag, or check runtime version through the CODESYS Development System if accessible, or inspect the installed package version via system package manager (dpkg, rpm, opkg depending on OS).Affected if The installed version is below 4.8.0.0 for any of the affected SL products listed.
-
Verify network communication is enabledCheck if CODESYS runtime is listening on network ports (typically ports 1217, 1218, 1743, 2455, or custom ports). Use 'netstat -tlnp' or 'ss -tlnp' to list listening services. Confirm remote communication is configured in the CODESYS Control configuration.Affected if The runtime accepts remote connections from network interfaces, as the vulnerability is exploitable by remote attackers sending malformed input.
-
Check for unauthenticated network exposureReview CODESYS runtime configuration for authentication settings and whether it allows unauthenticated or anonymous connections. Inspect config files in the CODESYS installation directory for security-related settings.Affected if The runtime allows unauthenticated remote communication, which is the attack vector for this improper input validation flaw.
The environment is affected if a CODESYS Control SL product is installed with version below 4.8.0.0 and the runtime is configured to accept remote network connections from untrusted sources.
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 vendor-provided patches for all affected CODESYS product versions and implement proper input validation controls on data received from untrusted sources.
CODESYS Control products version 4.8.0.0 or later (specific to each product: Control for Linux SL, Control for PFC200 SL, Control for PFC100 SL, Control for PLCnext SL, Control for Raspberry Pi SL, Control for Beaglebone SL, Control for Empc A/imx6 SL, Control for IOT2000 SL)
- 1. Identify the specific CODESYS Control product (e.g., Control for Linux SL, Control for PFC200 SL, etc.) from the affected list
- 2. Access the CODESYS customer portal at customers.codesys.com
- 3. Navigate to the downloads or patches section for your specific product
- 4. Download version 4.8.0.0 or later of the affected CODESYS Control product
- 5. Backup the current configuration and runtime files before upgrading
- 6. Stop the currently running CODESYS Control service
- 7. Install the updated version (4.8.0.0 or later) following the vendor's installation documentation
- 8. Restart the CODESYS Control service
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-47391 — 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-47391 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