CVE-2015-2847
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 · uneditedHoneywell Tuxedo Touch before 5.2.19.0_VA relies on client-side authentication involving JavaScript, which allows remote attackers to bypass intended access restrictions by removing USERACCT requests from the client-server data stream.
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 confidenceThe Honeywell Tuxedo Touch controller before version 5.2.19.0_VA performs authentication checks in client-side JavaScript rather than validating credentials server-side. An attacker can intercept the HTTP traffic between client and server and remove the USERACCT request, bypassing the authentication mechanism entirely.
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<= 5.1.13.0_vaCVSS 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
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/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.
-
Identify Honeywell Tuxedo Touch device on the networkScan the network for devices responding to HTTP on ports 80/443 or perform an Nmap scan looking for the Honeywell Tuxedo Touch web interface (typically port 80/tcp). Check network device inventories for the Tuxedo Touch controller.Affected if A Honeywell Tuxedo Touch controller is present and its web interface is reachable on the network.
-
Determine the firmware versionAccess the Tuxedo Touch web interface via HTTP and navigate to the system information or About page to view the firmware version, or use the Nmap script http-headers to check for version information in HTTP responses: nmap -p 80 --script http-headers <target-ip>Affected if The firmware version is 5.1.13.0_va or below, or any version prior to 5.2.19.0_VA.
-
Verify web interface accessibilityConfirm the Tuxedo Touch web interface is accessible from network segments where untrusted users or systems could intercept HTTP traffic. Attempt to access the login page via HTTP (not HTTPS).Affected if The web interface is accessible over HTTP without network restrictions that would prevent an attacker from intercepting or modifying traffic.
-
Inspect HTTP authentication behaviorUse a web proxy (such as Burp Suite or OWASP ZAP) to capture login requests. Observe if the authentication relies on client-side JavaScript validation by examining the HTTP responses for JavaScript-based auth checks, and test whether removing the USERACCT parameter from the request allows access.Affected if The authentication flow depends on client-side JavaScript validation and the USERACCT request parameter can be omitted to bypass authentication.
The environment is affected if a Honeywell Tuxedo Touch controller with firmware at or below version 5.1.13.0_va (or any version before 5.2.19.0_VA) has its web interface accessible on the network, as the client-side authentication can be bypassed by intercepting and modifying HTTP traffic.
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 dataNetwork-segment the affected device behind a firewall restricting all web access, or upgrade to firmware 5.2.19.0_VA if available from Honeywell. Consider replacing the device if firmware updates are no longer available.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-2847 — 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-2847 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