CVE-2017-5143
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. A user without authenticating can make a directory traversal attack by accessing a specific URL.
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 confidenceA directory traversal vulnerability in Honeywell XL Web II and XLWeb 500 controllers allows unauthenticated remote attackers to access arbitrary files on the filesystem by manipulating URL path traversal sequences in specific URLs.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- Low
CVSS:3.0/AV:N/AC:L/PR:N/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 Honeywell XL Web controller on networkScan the network for devices running HTTP/HTTPS on ports 80 or 443 that present a Honeywell XL Web or XLWeb 500 controller interface. Check banner or login page for 'XL Web' branding.Affected if The device is a Honeywell XL Web II or XLWeb 500 controller accessible on the network.
-
Check firmware versionAccess the controller web interface and navigate to System Information, About, or Status page. Look for the xlwebexe version number.Affected if The installed xlwebexe version equals exactly '1-02-08' or '2-01-00'.
-
Verify web interface accessibilityConfirm the controller web interface is reachable via HTTP/HTTPS from network segments outside the control system DMZ.Affected if The web interface is exposed to untrusted network segments without firewall filtering.
-
Inspect web server logs for traversal attemptsIf accessible, review web server logs or IDS/IPS alerts for requests containing '../' or '..\' path sequences targeting sensitive files like '/etc/passwd' or 'C:\Windows\'.Affected if Log evidence shows directory traversal URL patterns directed at the controller.
You are affected if you have a Honeywell XL Web II or XLWeb 500 controller with xlwebexe version 1-02-08 or 2-01-00 that has its web interface network-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 dataRestrict network exposure of the affected controllers, implement proper input validation on URL path parameters, and apply vendor-supplied patches to upgrade to patched firmware versions.
- Consultation6.0 h
- Implementation4.0 h
- Testing8.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 $6,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5143 — 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-5143 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