CVE-2018-10603
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 · uneditedMartem TELEM GW6 and GWM devices with firmware 2018.04.18-linux_4-01-601cb47 and prior do not perform authentication of IEC-104 control commands, which may allow a rogue node a remote control of the industrial process.
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 confidenceMartem TELEM GW6 and GWM devices with firmware 2018.04.18 and prior contain a critical authentication bypass vulnerability in the IEC-104 protocol implementation. The devices fail to authenticate IEC-104 control commands, allowing any node that can reach the device to send control commands without any credentials or validation, potentially enabling complete remote control of connected industrial processes.
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<= 2018.04.18-linux_4-01-601cb47<= 2018.04.18-linux_4-01-601cb47CVSS 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 the device modelAccess the device management interface or check device documentation/labels to confirm the exact model is Martem Telem GW6 or GWMAffected if Device is a Martem Telem GW6 or GWM
-
Check the firmware versionLog into the device web interface or use the device's CLI command to retrieve the firmware version (commonly shown in system info or about page)Affected if Firmware version is 2018.04.18-linux_4-01-601cb47 or earlier
-
Confirm IEC-104 protocol is enabledCheck the device configuration for IEC-104 protocol settings, typically found in protocol or communication settings; verify the IEC-104 listener is activeAffected if IEC-104 protocol is enabled and listening on the network
-
Verify network accessibility to IEC-104 portPerform a network scan from an external host to check if port 2404 (standard IEC-104 port) is accessible, or review firewall rules protecting the deviceAffected if The IEC-104 port (typically 2404/TCP) is reachable from untrusted network segments
You are affected if you have a Martem Telem GW6 or GWM device running firmware version 2018.04.18 or earlier with IEC-104 protocol enabled and 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.
From vendor dataImmediately restrict network access to TELEM devices using firewalls or network segmentation, and contact Martem for patched firmware that implements IEC-104 authentication. Deploy IEC-104 protocol-aware intrusion detection to monitor for unauthorized control command attempts.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-10603 — 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-10603 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