dbcve.org
Control For Beaglebone SlApplication · Codesys

CVE-2022-47380

HIGH · 8.8 CVSS v3.1 Published 2023-05-15
Fix available
A fix is available. Upgrade to 4.8.0.0 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
An authenticated remote attacker may use a stack based  out-of-bounds write vulnerability in multiple CODESYS products in multiple versions to write data into the stack which can lead to a denial-of-service condition, memory overwriting, or remote code execution.

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 confidence

CODESYS products contain a stack-based buffer overflow vulnerability allowing authenticated remote attackers to write data beyond stack buffer boundaries. This can cause denial of service, memory corruption, or potentially remote code execution. The vulnerability affects multiple product versions and requires authentication to exploit.

MitigationApply vendor-supplied patches from CODESYS GmbH for all affected products and versions. Test patches in a non-production environment before deployment to verify compatibility with control system operations.

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
Control For Beaglebone SlApplication
Affected:< 4.8.0.0
Control For Empc A\/imx6 SlApplication
Affected:< 4.8.0.0
Control For Iot2000 SlApplication
Affected:< 4.8.0.0
Control For Linux SlApplication
Affected:< 4.8.0.0
Control For Pfc100 SlApplication
Affected:< 4.8.0.0
Control For Pfc200 SlApplication
Affected:< 4.8.0.0
Control For Plcnext SlApplication
Affected:< 4.8.0.0
Control For Raspberry Pi SlApplication
Affected:< 4.8.0.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed CODESYS product
    Locate the CODESYS Control runtime on the device. Check for product-specific processes or services such as 'CODESYS Control for Raspberry Pi', 'CODESYS Control for Linux', or similar. Inspect the installation directory or package list for the exact product name.
    Affected if The product name matches one of the affected products: Beaglebone, Empc A/imx6, IoT2000, Linux, PFC100, PFC200, PLCnext, or Raspberry Pi.
  2. Determine the installed CODESYS version
    Access the CODESYS Runtime information via the web management interface (typically port 8080 or 8443), or check the product version through the runtime configuration tool or installed package metadata. Look for the runtime version in the system information or about page.
    Affected if The installed version is lower than 4.8.0.0.
  3. Verify remote authentication is enabled
    Check if the CODESYS web server or network service is accessible remotely and confirm that user authentication is configured. Review the CmpWebServer settings or network configuration files to see if remote connections are permitted.
    Affected if The remote web interface or network service is exposed and authentication is configured, making exploitation possible.

A system is affected if it runs any of the listed CODESYS Control products with a version lower than 4.8.0.0 and has remote access or the web interface enabled for authenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 4.8.0.0 or later
Fixed in 4.8.0.0
Interim mitigation

Apply vendor-supplied patches from CODESYS GmbH for all affected products and versions. Test patches in a non-production environment before deployment to verify compatibility with control system operations.

Recommended fix High confidence

CODESYS Control products version 4.8.0.0 or later

  1. 1. Identify the specific CODESYS Control product (e.g., Control for Linux, Control for Raspberry Pi, etc.) running in your environment
  2. 2. Check the current installed version of the CODESYS Control product
  3. 3. If the version is below 4.8.0.0, download the updated version 4.8.0.0 or later from the official CODESYS customer portal at customers.codesys.com
  4. 4. Review the release notes for version 4.8.0.0 to confirm the security fix for CVE-2022-47380 is included
  5. 5. Schedule a maintenance window to apply the update
  6. 6. Before applying to production systems, test the upgrade in a staging or development environment
  7. 7. Apply the upgrade following the standard CODESYS installation procedure
  8. 8. After upgrade, verify the new version is correctly installed and the service is running

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Control For Beaglebone Sl Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-47380 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-47380 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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