CVE-2018-10627
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 · uneditedEchelon SmartServer 1 all versions, SmartServer 2 all versions prior to release 4.11.007, i.LON 100 all versions, and i.LON 600 all versions. An attacker can use the SOAP API to retrieve and change sensitive configuration items such as the usernames and passwords for the Web and FTP servers. This vulnerability does not affect the i.LON 600 product.
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 vulnerability allows attackers to exploit the SOAP API on Echelon SmartServer devices to retrieve and modify sensitive configuration items including usernames and passwords for Web and FTP servers. This authentication bypass enables full compromise of administrative 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 dataall versions< 4.11.007all versionsCVSS 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 the device modelAccess the device web interface or check the device label to confirm whether it is an Echelon SmartServer 1, SmartServer 2, or I.lon 100. This determines which version range applies.Affected if The device is a SmartServer 1, SmartServer 2 (any version), or I.lon 100.
-
Check the installed firmware versionLog into the device administrative interface and navigate to the firmware or system information section. For SmartServer 2, compare the version number to 4.11.007. For SmartServer 1 and I.lon 100, note that all versions are affected.Affected if SmartServer 2 firmware is below version 4.11.007, or the device is SmartServer 1 or I.lon 100 (any version).
-
Verify SOAP API accessibilityDetermine if the SOAP API endpoint is reachable from untrusted networks. Attempt a curl or HTTP request to the SOAP service port (typically port 80/443 on the device) and verify whether authentication is required or can be bypassed.Affected if The SOAP API is exposed to untrusted networks without proper authentication controls.
-
Review administrative credentialsCheck the Web and FTP server user accounts in the device configuration. Look for any unexpected usernames, modified passwords, or accounts that were not created by authorized administrators.Affected if Unknown or unauthorized administrative accounts exist, or if existing credentials have been altered without authorization.
-
Check for signs of exploitationReview device logs, audit trails, or network traffic logs for suspicious SOAP API requests, particularly those retrieving configuration files, user lists, or credential data.Affected if Logs show unauthorized or anomalous SOAP API queries retrieving sensitive configuration data.
A user is affected if they have a SmartServer 1 or I.lon 100 (any firmware), or a SmartServer 2 with firmware below 4.11.007, and the SOAP API 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.
From vendor data4.11.007
Upgrade SmartServer 2 to release 4.11.007 or later. For SmartServer 1, i.LON 100, and i.LON 600 (if impacted), restrict network access to the SOAP API, implement strong authentication, and contact the vendor for patches.
- Consultation8.0 h
- Implementation16.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 $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-10627 — 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-10627 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