Honeywell Tuxedo Touch up to 5.2.19.0 USERACCT Request access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Honeywell Tuxedo Touch up to 5.2.19.0 and classified as critical. The affected element is an unknown function of the component USERACCT Request Handler. Such manipulation leads to access control. This vulnerability is listed as CVE-2015-2847. In addition, an exploit is available. It is suggested to upgrade the affected component.
Details
A vulnerability, which was classified as critical, has been found in Honeywell Tuxedo Touch up to 5.2.19.0. Affected by this issue is an unknown code of the component USERACCT Request Handler. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. Impacted is confidentiality, integrity, and availability. CVE summarizes:
Honeywell 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.
The weakness was presented 07/26/2015 (Website). The advisory is shared for download at kb.cert.org. This vulnerability is handled as CVE-2015-2847. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details are unknown but a public exploit is available. The MITRE ATT&CK project declares the attack technique as T1068.
It is declared as proof-of-concept.
Upgrading to version 5.2.19.0_VA eliminates this vulnerability.
The vulnerability is also documented in the databases at SecurityFocus (BID 76035†) and Vulnerability Center (SBV-51639†). See VDB-76809 for similar entry. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
- 5.2.0
- 5.2.1
- 5.2.2
- 5.2.3
- 5.2.4
- 5.2.5
- 5.2.6
- 5.2.7
- 5.2.8
- 5.2.9
- 5.2.10
- 5.2.11
- 5.2.12
- 5.2.13
- 5.2.14
- 5.2.15
- 5.2.16
- 5.2.17
- 5.2.18
- 5.2.19.0
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 6.6
VulDB Base Score: 7.3
VulDB Temp Score: 6.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Access controlCWE: CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Tuxedo Touch 5.2.19.0_VA
Timeline
04/03/2015 🔍07/26/2015 🔍
07/26/2015 🔍
07/26/2015 🔍
07/28/2015 🔍
07/28/2015 🔍
11/05/2024 🔍
Sources
Advisory: kb.cert.orgStatus: Confirmed
CVE: CVE-2015-2847 (🔍)
GCVE (CVE): GCVE-0-2015-2847
GCVE (VulDB): GCVE-100-76808
CERT: 🔍
SecurityFocus: 76035
Vulnerability Center: 51639 - Honeywell Tuxedo Touch Remote Bypass Security by Removing USERACCT Requests, Medium
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 07/28/2015 10:17Updated: 11/05/2024 11:14
Changes: 07/28/2015 10:17 (52), 08/03/2017 03:25 (6), 06/03/2022 20:35 (3), 11/05/2024 11:14 (17)
Complete: 🔍
Cache ID: 216:D73:103
No comments yet. Languages: en.
Please log in to comment.