Comcast MX011ANM MX011AN_2.9p6s1_PROD_sey Signature access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Comcast MX011ANM MX011AN_2.9p6s1_PROD_sey and classified as problematic. This vulnerability affects unknown code. Executing a manipulation can lead to access control (Signature). This vulnerability appears as CVE-2017-9498. The attack requires local access. There is no available exploit.
Details
A vulnerability was found in Comcast MX011ANM MX011AN_2.9p6s1_PROD_sey. It has been declared as problematic. This vulnerability affects an unknown code. The manipulation with an unknown input leads to a access control vulnerability (Signature). The CWE definition for the vulnerability is CWE-264. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
The Comcast firmware on Motorola MX011ANM (firmware version MX011AN_2.9p6s1_PROD_sey) and Xfinity XR11-20 Voice Remote devices allows local users to upload arbitrary firmware images to an XR11 by leveraging root access. In other words, there is no protection mechanism involving digital signatures for the firmware.
The bug was discovered 07/30/2017. The weakness was presented 07/31/2017 (Website). The advisory is shared for download at github.com. This vulnerability was named CVE-2017-9498 since 06/07/2017. The exploitation appears to be easy. The attack needs to be approached locally. No form of authentication is required for a successful exploitation. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1068.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
See VDB-104667, VDB-104666, VDB-104665 and VDB-104664 for similar entries. 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: 5.4VulDB Meta Temp Score: 5.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
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: SignatureClass: Access control / Signature
CWE: CWE-264
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
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
06/07/2017 🔍07/30/2017 🔍
07/30/2017 🔍
07/31/2017 🔍
07/31/2017 🔍
11/02/2019 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2017-9498 (🔍)
GCVE (CVE): GCVE-0-2017-9498
GCVE (VulDB): GCVE-100-104668
See also: 🔍
Entry
Created: 07/31/2017 09:56Updated: 11/02/2019 15:22
Changes: 07/31/2017 09:56 (56), 11/02/2019 15:22 (1)
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.