CVE-2023-6357
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 · uneditedA low-privileged remote attacker could exploit the vulnerability and inject additional system commands via file system libraries which could give the attacker full control 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 confidenceThis is a command injection vulnerability where a low-privileged remote attacker can inject arbitrary system commands through file system library functions that improperly handle user input, potentially achieving full device compromise.
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.11.0.0< 4.11.0.0< 4.11.0.0< 4.11.0.0< 4.11.0.0< 4.11.0.0< 4.11.0.0< 4.11.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
- 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 the installed Codesys Control productLocate the product name on the device or in the system documentation. This could be in /etc/codesys, /opt/codesys, or the device's control panel.Affected if The product matches one of the affected variants: Beaglebone Sl, Empc A/imx6, Iot2000 Sl, Linux Arm Sl, Linux Sl, Pfc100 Sl, Pfc200 Sl, or Plcnext Sl.
-
Determine the installed version of Codesys ControlCheck the version number in the product's About section, control runtime logs, or by running the command 'codesyscontrol --version' or inspecting the installed package metadata.Affected if The version is lower than 4.11.0.0.
-
Verify if the file system library functions are accessibleInspect the installed Codesys library files in the library directory (typically /CODESYS/Libraries or similar) and check if the file system-related function blocks are loaded in the runtime.Affected if The file system library functions are present and actively used in the runtime configuration.
-
Check for user-accessible file operation interfacesReview the PLC application configuration and any exposed interfaces (Web Server, FTP, SNMP, or custom user-defined functions) that accept file path inputs from remote users.Affected if Remote or low-privileged users can supply file paths to the system through any exposed interface.
You are affected if you are running any of the listed Codesys Control variants at a version below 4.11.0.0 and the file system library functions are accessible to remote or low-privileged users.
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.11.0.0
Implement strict input validation and sanitization for all file system operations; replace string concatenation in system calls with parameterized APIs; apply principle of least privilege to the application process.
Control For all products (Beaglebone, Empc A/imx6, Iot2000, Linux Arm, Linux, Pfc100, Pfc200, Plcnext) - upgrade to version 4.11.0.0 or later
- 1. Identify the specific Control For product in use (Beaglebone, Empc A/imx6, Iot2000, Linux Arm, Linux, Pfc100, Pfc200, or Plcnext)
- 2. Obtain the appropriate update/package for Control For version 4.11.0.0 or later from the official vendor (Siemens or VDE cert source)
- 3. Before applying the update, backup current configuration if possible
- 4. Apply the upgrade to version 4.11.0.0 or later following vendor documentation
- 5. Verify the upgrade was successful and the service is functioning properly
- 6. Confirm the OS command injection vulnerability is resolved by ensuring the file system libraries no longer permit arbitrary command injection
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation16.0 h
- Testing12.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 $11,136.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-6357 — 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-2023-6357 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