CVE-2018-20025
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 · uneditedUse of Insufficiently Random Values exists in CODESYS V3 products versions prior V3.5.14.0.
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 confidenceThe CODESYS V3 products use insufficiently random values in security-critical operations. This predictability weakness could allow attackers to guess or brute-force random values used for session identification, tokens, or other cryptographic operations, potentially leading to unauthorized access or session hijacking.
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, < 3.5.14.0>= 3.0, < 3.5.14.0>= 3.0, < 3.5.14.0>= 3.0, < 3.5.14.0>= 3.0, < 3.5.14.0>= 3.0, < 3.5.14.0>= 3.0, < 3.5.14.0>= 3.0, < 3.5.14.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
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 CODESYS Control productCheck which CODESYS Control runtime is installed on the system by inspecting the installed software list, runtime services, or the product-specific web interface (typically accessible on port 8080 or 443)Affected if The system runs one of the following: Codesys Control For Beaglebone Sl, Codesys Control For Empc A/imx6 Sl, Codesys Control For Iot2000 Sl, Codesys Control For Linux Sl, Codesys Control For Pfc100 Sl, Codesys Control For Pfc200 Sl, Codesys Control For Raspberry Pi Sl, or Codesys Control Rte Sl
-
Determine the installed versionLocate the runtime version through the product's web management interface, CODESYS Development System (Project > Show Device), or by checking the runtime package information on the target deviceAffected if The installed version is 3.0 or higher but lower than 3.5.14.0
-
Check if remote/web interfaces are enabledExamine whether the CODESYS web server, OPC UA server, or other network-facing services are enabled and accessible on the deviceAffected if Remote management interfaces (web server, OPC UA) are enabled and exposed on the network
-
Verify active session handlingInspect the runtime configuration for session management settings or examine active connections through the web management interface or network monitoringAffected if The runtime is handling remote client connections or web-based management sessions
A system is affected if it runs any of the listed CODESYS Control products with version 3.0 through 3.5.13.x and has network-accessible interfaces enabled that handle authentication sessions or tokens.
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.
From vendor data3.5.14.0
Upgrade CODESYS V3 products to version V3.5.14.0 or later, which contains proper random value generation. For systems that cannot be immediately updated, implement additional monitoring for anomalous access patterns and consider network segmentation to limit exposure.
- Consultation8.0 h
- Implementation12.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 $10,624.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-20025 — 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-20025 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