CVE-2018-10607
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 allow the creation of new connections to one or more IOAs, without closing them properly, which may cause a denial of service within the industrial process control channel.
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 confidenceMartem TELEM GW6 and GWM devices with firmware 2018.04.18-linux_4-01-601cb47 and prior contain a resource management flaw where new connections to IOAs (Input/Output Aggregators) are created without being properly closed, leading to resource exhaustion and denial of service in the industrial process control channel.
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
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 modelLocate the Martem device on the network and confirm it is either a TELEM GW6 or GWM model. Check the device label, management interface, or SNMP inventory for the exact model designation.Affected if The device is not a GW6 or GWM model.
-
Determine the installed firmware versionAccess the device management interface or use the vendor-supplied diagnostic tool to retrieve the firmware version string. Compare it against the affected version 2018.04.18-linux_4-01-601cb47 or earlier.Affected if The firmware version is 2018.04.18-linux_4-01-601cb47 or any earlier version.
-
Verify if the device is network accessibleCheck network exposure by reviewing firewall rules, ACLs, or network segmentation. Confirm whether the device management or IOA communication ports are reachable from untrusted networks.Affected if The device is directly accessible from broader network segments without filtering.
-
Inspect for connection accumulationMonitor the device's active connection count over time using netstat, SNMP connection tables, or the vendor management interface. Look for connections to IOAs (Input/Output Aggregators) that persist and grow without being released.Affected if Connection count to IOAs increases steadily without returning to baseline, indicating a connection leak.
-
Check for service degradation symptomsReview system logs, SNMP performance metrics (CPU, memory), or the industrial control channel status for signs of denial of service such as dropped messages, timeouts, or process control interruptions.Affected if The industrial process control channel shows packet loss, delayed responses, or the device becomes unresponsive under normal connection load.
The environment is affected if the device is a Martem TELEM GW6 or GWM running firmware version 2018.04.18-linux_4-01-601cb47 or earlier, and the device is network-accessible with IOA connections enabled.
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 dataApply vendor-supplied firmware update to version newer than 2018.04.18; implement network segmentation and monitoring to detect connection anomalies as compensating controls until firmware can be updated.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-10607 — 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-10607 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