CVE-2018-10612
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 3S-Smart Software Solutions GmbH CODESYS Control V3 products prior to version 3.5.14.0, user access management and communication encryption is not enabled by default, which could allow an attacker access to the device and sensitive information, including user credentials.
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 confidenceCODESYS Control V3 products prior to version 3.5.14.0 ship with user access management and TLS/SSL communication encryption disabled by default, allowing unauthenticated attackers on the network to access the device directly and harvest user credentials.
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
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/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 CODESYS Control V3 installed versionLocate the CODESYS Control runtime installation and retrieve its version number, typically found in the product's about dialog, installation directory, or runtime configuration fileAffected if Installed version is 3.0 or higher but lower than 3.5.14.0
-
Locate user access management configurationAccess the CODESYS Control V3 configuration interface or configuration file where user access management settings are storedAffected if User access management is disabled or not explicitly configured (default state)
-
Verify TLS/SSL communication encryption statusCheck the CODESYS Control V3 configuration for communication encryption settings, typically found in security or network configuration sectionsAffected if TLS/SSL encryption for communications is disabled or not configured (default state)
-
Assess network accessibilityDetermine if the CODESYS Control device is directly accessible from the network without authentication barriersAffected if Device is reachable on the network with user access management disabled, allowing unauthenticated access
A user is affected if the installed CODESYS Control V3 version falls within 3.0 to less than 3.5.14.0 AND either user access management or TLS/SSL encryption (or both) remain in their default disabled state, especially if the device is network-accessible.
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.14.0
Enable user access management and configure communication encryption (TLS/SSL) in the CODESYS Control V3 configuration for all affected installations.
CODESYS Control V3 version 3.5.14.0 or later
- 1. Identify all deployed CODESYS Control V3 instances in the environment
- 2. Back up current configurations and project files
- 3. Obtain CODESYS Control V3 version 3.5.14.0 or later from 3S-Smart Software Solutions
- 4. Upgrade each affected instance to version 3.5.14.0 or newer
- 5. After upgrade, verify that user access management and communication encryption are properly enabled according to product documentation
- 6. Change all user credentials as a precautionary measure since they may have been exposed
- 7. Review and apply any additional security hardening recommendations from the vendor
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-10612 — 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-10612 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