CVE-2015-0984
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 · uneditedDirectory traversal vulnerability in the FTP server on Honeywell Excel Web XL1000C50 52 I/O, XL1000C100 104 I/O, XL1000C500 300 I/O, XL1000C1000 600 I/O, XL1000C50U 52 I/O UUKL, XL1000C100U 104 I/O UUKL, XL1000C500U 300 I/O UUKL, and XL1000C1000U 600 I/O UUKL controllers before 2.04.01 allows remote attackers to read files under the web root, and consequently obtain administrative login access, via a crafted pathname.
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 confidenceDirectory traversal vulnerability in the FTP server on Honeywell Excel Web XL1000C series controllers allows remote attackers to use '..' sequences in crafted pathnames to escape the web root and read arbitrary files, potentially exposing administrative login credentials stored in configuration files.
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<= 2.04.00<= 2.04.00<= 2.04.00<= 2.04.00<= 2.04.00<= 2.04.00<= 2.04.00<= 2.04.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
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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 controller modelLocate the physical or network documentation for the Honeywell controller and confirm the exact model number (e.g., XL1000C100, XL1000C1000, XL1000C50) matches one of the affected products listedAffected if Model is one of the Honeywell Excel Web XL1000C series variants
-
Determine the firmware versionAccess the controller's web interface or administrative console and locate the firmware/software version information. This is typically found under System Info, About, or Maintenance settingsAffected if Installed version is 2.04.00 or lower (any version <= 2.04.00)
-
Verify FTP server is enabledCheck the controller configuration settings to confirm the FTP server service is active. This may be visible in Network Services, Server Settings, or FTP configuration panelsAffected if FTP server is enabled and running on the controller
-
Confirm network accessibilityAttempt to reach the FTP service on the controller from your workstation or use a network scan to verify the FTP port (typically port 21) is open and reachable from the networkAffected if FTP service is accessible from network segments that are not restricted to trusted administrators
A defender is affected if they use a Honeywell Excel Web XL1000C series controller with firmware version 2.04.00 or lower and the FTP server is enabled and 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.
dbcve · scopedApply vendor patch version 2.04.01 or later to the affected controllers; until patched, restrict network access to the FTP server and monitor for unauthorized access attempts.
Firmware version 2.04.01 or later
- 1. Identify the specific Honeywell Excel Web XL model number (XL1000C50, XL1000C100, XL1000C500, XL1000C1000, or their UUKL variants) in your environment
- 2. Check the current firmware version on the affected controller via the web interface or console
- 3. Download firmware version 2.04.01 or later from the official Honeywell website or through authorized vendor channels
- 4. Review Honeywell's firmware update documentation and ensure backup of current configuration
- 5. Apply the firmware update following Honeywell's published upgrade procedure for the specific controller model
- 6. After reboot, verify the firmware version has been updated to 2.04.01 or later
- 7. Confirm the vulnerability is no longer present by testing that directory traversal requests are rejected
- 8. As an additional mitigation, restrict network access to the FTP server and place the device behind a firewall or in a DMZ
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0984 — 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-2015-0984 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