dbcve.org
Homelynk Controller Lss100100 FirmwareOperating system · Schneider Electric

CVE-2017-7689

CRITICAL · 9.8 CVSS v3.1 Published 2017-04-11
Fix available
A fix is available. Upgrade to 1.5.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
A Command Injection vulnerability in Schneider Electric homeLYnk Controller exists in all versions before 1.5.0.

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 confidence

A command injection vulnerability exists in the Schneider Electric homeLYnk Controller, a building automation device. The vulnerability allows attackers to execute arbitrary OS commands on the device, likely through unsanitized input in the web interface or API. All versions prior to 1.5.0 are affected.

MitigationUpgrade the homeLYnk Controller firmware to version 1.5.0 or later to remediate this vulnerability. If immediate patching is not possible, network segmentation and restricting web interface access to trusted networks can reduce exposure.

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
Homelynk Controller Lss100100 FirmwareOperating system
Affected:< 1.5.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Access the device web interface or check the device label/documentation to confirm it is a Schneider Electric Homelynk Controller model Lss100100.
    Affected if The device is a Schneider Electric Homelynk Controller Lss100100.
  2. Determine the firmware version
    Log into the web interface and navigate to the 'About' or 'System Information' page to view the installed firmware version. Alternatively, check the device documentation for the specific method to retrieve the firmware version.
    Affected if The installed firmware version is prior to 1.5.0 (e.g., 1.4.x, 1.3.x, etc.).
  3. Check web interface accessibility
    Attempt to access the device web interface over HTTP/HTTPS from a browser. Verify if the login page or unauthenticated endpoints are reachable.
    Affected if The web interface is exposed and accessible to network attackers.
  4. Verify command injection input vectors
    If accessible, examine the web interface or API endpoints for input fields that may accept and process OS commands. Look for fields related to network configuration, system commands, or diagnostics that might pass unsanitized input to system calls.
    Affected if Unsanitized input fields exist in the web interface or API that could accept arbitrary OS commands.

You are affected if you have a Schneider Electric Homelynk Controller Lss100100 running firmware version prior to 1.5.0 with an accessible web interface containing exploitable input fields.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.5.0 or later
Fixed in 1.5.0
Interim mitigation

Upgrade the homeLYnk Controller firmware to version 1.5.0 or later to remediate this vulnerability. If immediate patching is not possible, network segmentation and restricting web interface access to trusted networks can reduce exposure.

Recommended fix High confidence

Firmware 1.5.0

  1. 1. Identify the current firmware version of the Homelynk Controller Lss100100 by accessing the device web interface or checking system information.
  2. 2. Navigate to the official Schneider Electric download portal at download.schneider-electric.com to obtain the firmware version 1.5.0 or later.
  3. 3. Review the firmware upgrade instructions provided by Schneider Electric before proceeding.
  4. 4. Create a backup of the current device configuration if the web interface provides export functionality.
  5. 5. Upload and apply firmware version 1.5.0 to the Homelynk Controller through the device's firmware upgrade interface.
  6. 6. After the upgrade completes, verify the device is operational and accessible.
  7. 7. Confirm the installed firmware version is 1.5.0 or later to ensure the vulnerability is remediated.
Caveat Firmware upgrades on OT devices may affect existing configurations; backup before upgrading and test in a non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Homelynk Controller Lss100100 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-7689 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-7689 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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