| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Phoenix Contact mGuard 8.4.0 and classified as critical. This affects an unknown function of the component Update Handler. Executing a manipulation can lead to resource injection (Reset). This vulnerability is registered as CVE-2017-5159. It is possible to launch the attack remotely. No exploit is available.
Details
A vulnerability classified as critical was found in Phoenix Contact mGuard 8.4.0. This vulnerability affects an unknown code of the component Update Handler. The manipulation with an unknown input leads to a resource injection vulnerability (Reset). The CWE definition for the vulnerability is CWE-99. The product receives input from an upstream component, but it does not restrict or incorrectly restricts the input before it is used as an identifier for a resource that may be outside the intended sphere of control. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
An issue was discovered on Phoenix Contact mGuard devices that have been updated to Version 8.4.0. When updating an mGuard device to Version 8.4.0 via the update-upload facility, the update will succeed, but it will reset the password of the admin user to its default value.
The bug was discovered 01/17/2017. The weakness was published 02/13/2017 (Website). The advisory is shared for download at securityfocus.com. This vulnerability was named CVE-2017-5159 since 01/03/2017. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are neither technical details nor an exploit publicly available.
The vulnerability was handled as a non-public zero-day exploit for at least 27 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 95648†). Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.5
VulDB Base Score: 7.3
VulDB Temp Score: 7.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
Name: ResetClass: Resource injection / Reset
CWE: CWE-99
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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
01/03/2017 🔍01/17/2017 🔍
01/17/2017 🔍
02/13/2017 🔍
02/13/2017 🔍
02/14/2017 🔍
12/18/2020 🔍
Sources
Advisory: securityfocus.com⛔Status: Not defined
CVE: CVE-2017-5159 (🔍)
GCVE (CVE): GCVE-0-2017-5159
GCVE (VulDB): GCVE-100-96940
SecurityFocus: 95648 - Phoenix Contact mGuard CVE-2017-5159 Security Bypass Vulnerability
OSVDB: - CVE-2017-5159 - Phoenix Contact - mGuard - Password Reset Issue
Entry
Created: 02/14/2017 09:19Updated: 12/18/2020 06:42
Changes: 02/14/2017 09:19 (64), 12/18/2020 06:42 (4)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.