CVE-2018-8855
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. The devices allow unencrypted Web connections by default, and devices can receive configuration and firmware updates by unsecure FTP.
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 confidenceEchelon SmartServer and i.LON building automation devices ship with unencrypted HTTP web interfaces and support unencrypted FTP for configuration and firmware updates. This allows attackers on the network to intercept credentials, inject malicious configurations, or replace firmware with compromised versions.
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 versionsall 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 Echelon SmartServer or i.LON devices on the networkScan the network for devices with product banners or MAC OUI matching Echelon manufacturing, or locate devices manually via asset inventoryAffected if Any Echelon SmartServer 1, SmartServer 2, I.lon 100, or I.lon 600 device is present on the network
-
Check if HTTP (port 80) is enabled on the deviceAttempt an HTTP connection to the device IP on port 80 (e.g., curl -I http://<device-ip>:80) or use a network port scanner to test port 80 availabilityAffected if HTTP responds on port 80, indicating the unencrypted web interface is active
-
Check if FTP (port 21) is enabled on the deviceAttempt an FTP connection to the device IP on port 21 (e.g., ftp <device-ip>) or use a network port scanner to test port 21 availabilityAffected if FTP responds on port 21, indicating the unencrypted FTP service is active
-
For SmartServer 2, determine the firmware versionLog into the device web interface or use SNMP/CLI to retrieve the firmware version string, then compare to the affected rangeAffected if The device is a SmartServer 2 with firmware version less than 4.11.007
The environment is affected if any Echelon device (SmartServer 1, I.lon 100, I.lon 600, or SmartServer 2 < 4.11.007) has HTTP port 80 or FTP port 21 accessible, as these unencrypted services allow credential interception or malicious configuration injection.
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
Enable HTTPS on the web interface, replace unencrypted FTP with SFTP/FTPS for firmware/config transfers, and network-segment these devices to limit exposure to untrusted networks.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.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,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-8855 — 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-8855 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