CVE-2018-25048
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 · uneditedThe CODESYS runtime system in multiple versions allows an remote low privileged attacker to use a path traversal vulnerability to access and modify all system files as well as DoS 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 confidenceThe CODESYS runtime system contains a path traversal vulnerability allowing remote low-privileged attackers to access and modify arbitrary system files on the host device, potentially leading to complete system compromise. Attackers can also cause Denial of Service. The vulnerability stems from insufficient input validation on file path parameters within the runtime.
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>= 3.0.0.0, < 3.5.12.30>= 3.0.0.0, < 3.5.12.30>= 3.0.0.0, < 3.5.12.30>= 3.0.0.0, < 3.5.12.30>= 3.0.0.0, < 3.5.12.30>= 3.0.0.0, < 3.5.12.30>= 3.0.0.0, < 3.5.12.30>= 3.0.0.0, < 3.5.12.30CVSS 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 installed CODESYS productCheck the system for installed CODESYS Control runtime packages. On Linux-based systems (Beaglebone, Raspberry Pi, IoT2000), check /etc/codesys3/packages or the package management system. On Windows (Control RTE), check Programs and Features or the CODESYS installation directory for product identification.Affected if The product is one of: Codesys Control For Beaglebone, Empc A/imx6, IoT2000, Pfc100, Pfc200, Raspberry Pi, Control Rte, or Control V3 Runtime System Toolkit
-
Determine installed CODESYS runtime versionAccess the CODESYS runtime information through the CODESYS Development System (connect to target device), check the runtime package version via package manager, or query the runtime via its web interface or configuration tool if available.Affected if The installed version is >= 3.0.0.0 and < 3.5.12.30
-
Verify CODESYS runtime network service is exposedCheck if the CODESYS runtime network ports (typically TCP ports 11740, 11741, or custom-configured ports) are listening on network interfaces accessible from untrusted networks. Use netstat or ss commands to list open ports and their binding addresses.Affected if The runtime network service is bound to interfaces accessible from untrusted or external networks (not isolated VLANs)
-
Check for file handling functionality enabledReview the CODESYS application configuration and running tasks to determine if file I/O operations (file read/write, file copy, or file transfer features) are implemented or enabled in the runtime environment.Affected if File handling features or web-based file management modules are enabled and exposed through the runtime
You are affected if you have any of the listed CODESYS Control products installed with a version >= 3.0.0.0 and < 3.5.12.30, and the runtime network service is accessible from your network.
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 · scoped3.5.12.30
Apply vendor patches for affected CODESYS runtime versions; implement strict network segmentation and access controls to limit exposure to untrusted networks; validate and sanitize all file path inputs within the application.
Upgrade to CODESYS Control version 3.5.12.30 or later
- Identify the specific CODESYS Control product from the affected list (Beaglebone, Empc A/imx6, Iot2000, Pfc100, Pfc200, Raspberry Pi, Control Rte, or Control V3 Runtime System Toolkit)
- Check the current installed version to confirm it is >= 3.0.0.0 and < 3.5.12.30
- Obtain the updated CODESYS runtime version 3.5.12.30 or later from the vendor (customers.codesys.com or official CODESYS distribution channels)
- Apply the upgrade following the vendor's documentation for the specific device/platform
- Verify the upgrade was successful by checking the runtime version
- Confirm the path traversal vulnerability is no longer present by testing file access restrictions
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-25048 — 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-2018-25048 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