| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Honeywell XL Web II and XLWeb 500 and classified as problematic. This issue affects some unknown processing of the component Password Storage. This manipulation causes access control. This vulnerability is registered as CVE-2017-5139. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability has been found in Honeywell XL Web II and XLWeb 500 (the affected version unknown) and classified as problematic. Affected by this vulnerability is an unknown part of the component Password Storage. The manipulation with an unknown input leads to a access control vulnerability. The CWE definition for the vulnerability is CWE-264. As an impact it is known to affect confidentiality. The summary by CVE is:
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. Any user is able to disclose a password by accessing a specific URL, because of Plaintext Storage of a Password.
The bug was discovered 02/02/2017. The weakness was published 02/13/2017 by Maxim Rupp (Website). The advisory is shared at securityfocus.com. This vulnerability is known as CVE-2017-5139 since 01/03/2017. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 11 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 95971†). Similar entries are available at VDB-96926, VDB-96927, VDB-96928 and VDB-96929. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.6
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
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-264
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
OpenVAS ID: 801599
OpenVAS Name: Honeywell XL Web Multiple Vulnerabilities
OpenVAS File: 🔍
OpenVAS Family: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
01/03/2017 🔍02/02/2017 🔍
02/02/2017 🔍
02/13/2017 🔍
02/13/2017 🔍
02/14/2017 🔍
08/14/2020 🔍
Sources
Advisory: securityfocus.com⛔Researcher: Maxim Rupp
Status: Not defined
CVE: CVE-2017-5139 (🔍)
GCVE (CVE): GCVE-0-2017-5139
GCVE (VulDB): GCVE-100-96925
SecurityFocus: 95971 - Honeywell XL Web II Controller Multiple Security Vulnerabilities
OSVDB: - CVE-2017-5139 - Honeywell - Multiple Products - Plaintext Password Issue
See also: 🔍
Entry
Created: 02/14/2017 09:17Updated: 08/14/2020 14:48
Changes: 02/14/2017 09:17 (62), 08/14/2020 14:48 (6)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.