dbcve.org
Xl Web Ii ControllerOperating system · Honeywell

CVE-2017-5142

CRITICAL · 9.1 CVSS v3.0 Published 2017-02-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
97/100
Remediation priority · Urgent
Remotely reachable 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
An 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. A user with low privileges is able to open and change the parameters by accessing a specific URL because of Improper Privilege Management.

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

This vulnerability in Honeywell XL Web II and XLWeb 500 controllers allows low-privilege users to access and modify parameters via specific URLs due to improper privilege management. The issue affects XLWebExe-2-01-00 and prior (XL1000C500) and XLWebExe-1-02-08 and prior (XLWeb 500), enabling unauthorized configuration changes.

MitigationApply vendor patches if available; if not, implement strict network segmentation to isolate ICS devices, enforce role-based access controls, and monitor for unauthorized URL access attempts.

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
Xl Web Ii ControllerOperating system
Affected:= xlwebexe-1-02-08= xlwebexe-2-01-00

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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
Low

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/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 checks

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

  1. Identify the XL Web controller model and firmware version
    Access the device web interface or check the system information page. Look for the XLWebExe version number displayed, typically found in the About or System Info section of the web interface.
    Affected if The version is xlwebexe-1-02-08 or earlier for XLWeb 500, or xlwebexe-2-01-00 or earlier for XL Web II (XL1000C500).
  2. Confirm the web interface is accessible
    Attempt to access the device web interface via HTTP/HTTPS on the configured IP address or hostname. Note whether the login page loads.
    Affected if The web interface responds and accepts connections, meaning the vulnerable web component is exposed.
  3. Verify low-privilege user access to sensitive URLs
    Log in with a standard (non-administrator) user account and attempt to access configuration URLs or parameters that should require elevated privileges. Common test paths include accessing system settings, network configuration, or controller parameters via direct URL access.
    Affected if Low-privilege users can view or modify parameters via direct URL access that should be restricted to administrator accounts.
  4. Check user role configuration
    Review the user account roles and permissions configured in the XL Web controller. Access the user management or access control section of the web interface to enumerate defined roles and their associated permissions.
    Affected if Multiple privilege levels exist but the system allows lower-privilege users to perform actions assigned to higher-privilege roles through specific URLs.

A user is affected if the device runs an affected XLWebExe version (1-02-08 or earlier for XLWeb 500, or 2-01-00 or earlier for XL Web II) and the web interface is accessible, allowing unauthorized configuration changes by low-privilege users via direct URL access.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches if available; if not, implement strict network segmentation to isolate ICS devices, enforce role-based access controls, and monitor for unauthorized URL access attempts.

Fix this in Xl Web Ii Controller Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-5142 — 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-5142 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