CVE-2017-6023
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 · uneditedAn issue was discovered in Fatek Automation PLC Ethernet Module. The affected Ether_cfg software configuration tool runs on the following Fatek PLCs: CBEH versions prior to V3.6 Build 170215, CBE versions prior to V3.6 Build 170215, CM55E versions prior to V3.6 Build 170215, and CM25E versions prior to V3.6 Build 170215. A stack-based buffer overflow vulnerability has been identified, which may allow remote code execution or crash the affected 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 · high confidenceA stack-based buffer overflow vulnerability exists in the Ether_cfg configuration tool for Fatek Automation PLC Ethernet modules (CBEH, CBE, CM55E, CM25E) prior to version V3.6 Build 170215. This flaw may allow remote code execution or cause the device to crash.
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.5<= 3.5<= 3.5<= 3.5CVSS 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.1/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 Fatek PLC Ethernet modules on the networkLocate any Fatek Automation PLC Ethernet modules (CBEH, CBE, CM55E, CM25E) connected to the network. These are typically found during network asset inventory or by identifying Fatek devices on subnet.Affected if Any CBEH, CBE, CM55E, or CM25E Ethernet module is present in the environment
-
Access the module firmware version via Ether_cfgOpen the Ether_cfg configuration tool and connect to each identified Fatek Ethernet module. Navigate to the module status or system information screen to view the current firmware version.Affected if The displayed firmware version is 3.5 or earlier (any version <= 3.5)
-
Verify firmware version via module web interface or status pageIf available, access the module directly through its web interface (if enabled) or check the status page to confirm the firmware version reported by the device itself.Affected if The device reports firmware version <= 3.5
-
Confirm the configuration tool is in useVerify that the Ether_cfg configuration tool is actively used or stored in the environment for managing Fatek PLC Ethernet modules.Affected if Ether_cfg is used to manage any Fatek Ethernet module and the module firmware is <= 3.5
The environment is affected if any Fatek CBEH, CBE, CM55E, or CM25E Ethernet module has firmware version 3.5 or earlier, as this version range contains the stack-based buffer overflow vulnerability.
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 · scopedUpdate the Ether_cfg firmware on affected Fatek PLC Ethernet modules to version V3.6 Build 170215 or later. If patching is not immediately possible, isolate affected devices from untrusted networks.
V3.6 Build 170215
- Identify the exact Fatek PLC Ethernet Module model (CBE, CBEH, CM25E, or CM55E) in use
- Check the current firmware version of the Ethernet Module through the Ether_cfg configuration tool or device management interface
- Download firmware version V3.6 Build 170215 from the official Fatek Automation support website or contact Fatek technical support to obtain the update
- Follow Fatek's official firmware update procedure to upgrade the Ethernet Module to V3.6 Build 170215
- Verify the firmware version has been successfully updated after the upgrade process
- Test the Ethernet Module functionality to ensure normal operation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-6023 — 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-2017-6023 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