CVE-2017-5141
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 Honeywell XL Web II controller XL1000C500 XLWebExe-2-01-00 and prior, and XLWeb 500 XLWebExe-1-02-08 and prior. An attacker can establish a new user session, without invalidating any existing session identifier, which gives the opportunity to steal authenticated sessions (SESSION FIXATION).
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 confidenceThis is a SESSION FIXATION vulnerability in Honeywell XL Web II and XLWeb 500 controller web interfaces. An attacker can establish a new user session without invalidating any existing session identifier, allowing them to potentially hijack authenticated user sessions after the victim logs in.
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= xlwebexe-1-02-08= xlwebexe-2-01-00CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- Low
CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:L
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 product and modelConfirm that the target system is a Honeywell XL Web II controller or XLWeb 500 controller. This is typically found in the system information page or by accessing the web interface login page and checking the product identification.Affected if The system is a Honeywell XL Web II or XLWeb 500 controller.
-
Check the installed XLWebExe versionLocate the xlwebexe version information. This may be displayed in the web interface header, system diagnostics page, or in the firmware/software inventory. Look for version strings matching xlwebexe-1-02-08 or xlwebexe-2-01-00.Affected if The installed version is exactly xlwebexe-1-02-08 or xlwebexe-2-01-00.
-
Verify the web interface is enabledAccess the web interface login page via HTTP/HTTPS on the device. Confirm the web service is running and responding. The vulnerability requires the web interface to be accessible.Affected if The web interface is active and reachable on the network.
-
Test session ID behavior on loginObtain a session identifier (cookie or URL parameter) before authentication, then authenticate with valid credentials. After successful login, examine whether the session identifier has been regenerated to a new value. If the original session ID persists, the vulnerability is present.Affected if The same session ID is retained after successful authentication instead of being regenerated to a new identifier.
A system is affected if it is a Honeywell XL Web II or XLWeb 500 controller running xlwebexe-1-02-08 or xlwebexe-2-01-00 with the web interface enabled and session IDs not regenerated upon login.
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 patches (XLWebExe-2-01-01 or later for XL1000C500, XLWebExe-1-02-09 or later for XLWeb 500) and implement session ID regeneration upon successful authentication.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5141 — 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-5141 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