CVE-2017-5157
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 · uneditedAn issue was discovered in Schneider Electric homeLYnk Controller, LSS100100, all versions prior to V1.5.0. The homeLYnk controller is susceptible to a cross-site scripting attack. User inputs can be manipulated to cause execution of JavaScript code.
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 confidenceReflected cross-site scripting (XSS) vulnerability in Schneider Electric homeLYnk Controller (LSS100100) web interface. User-supplied input is not properly sanitized before being rendered in the response, allowing attackers to inject malicious JavaScript code that executes in the context of the victim's browser session.
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= 1.3.0CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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.
-
Confirm the device modelIdentify if the target system is a Schneider Electric homeLYnk Controller LSS100100 by checking the device label, web interface banner, or SNMP/sysinfo dataAffected if The device is confirmed to be a Homelynk Controller LSS100100
-
Check the installed firmware versionAccess the web interface and navigate to the About or System Information page to view the firmware version, or use the device's API/CLI if available to query the firmware versionAffected if The firmware version is 1.3.0 (exact match as listed in affected versions)
-
Verify the web interface is accessibleConfirm the web interface (HTTP/HTTPS) is reachable on the device by attempting to access the login page or common endpointsAffected if The web interface is exposed and accessible on the network
-
Review web server logs for XSS indicatorsExamine the device logs or any available web server access logs for unusual query parameters or payloads that may indicate XSS exploitation attempts (e.g., <script> tags, event handlers, JavaScript URIs)Affected if Log entries contain suspicious patterns typical of XSS probes or successful XSS exploitation
A user is affected if they have a Schneider Electric homeLYnk Controller LSS100100 running firmware version 1.3.0 with the web interface enabled and 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 dataUpgrade homeLYnk Controller to firmware V1.5.0 or later, which contains the security fix. If immediate upgrade is not feasible, implement input validation and output encoding on all user-facing web application endpoints to neutralize XSS payloads.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5157 — 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-2017-5157 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