| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, was found in Milwaukee ONE-KEY on Android. The impacted element is an unknown function of the component Bearer Token. Such manipulation leads to 7pk security. This vulnerability is uniquely identified as CVE-2017-3215. The attack can be launched remotely. No exploit exists.
Details
A vulnerability, which was classified as problematic, has been found in Milwaukee ONE-KEY on Android (Android App Software) (affected version not known). Affected by this issue is some unknown functionality of the component Bearer Token. The manipulation with an unknown input leads to a 7pk security vulnerability. Using CWE to declare the problem leads to CWE-254. Impacted is confidentiality, integrity, and availability. CVE summarizes:
The Milwaukee ONE-KEY Android mobile application uses bearer tokens with an expiration of one year. This bearer token, in combination with a user_id can be used to perform user actions.
The bug was discovered 06/19/2017. The weakness was disclosed 06/20/2017 (Website). The advisory is shared for download at duo.com. This vulnerability is handled as CVE-2017-3215 since 12/05/2016. The exploitation is known to be difficult. The attack may be launched remotely. No form of authentication is required for exploitation. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1211.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entry VDB-102691 is pretty similar. Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
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.6
VulDB Temp Score: 5.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.3
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: 7pk securityCWE: CWE-254
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
12/05/2016 🔍06/19/2017 🔍
06/19/2017 🔍
06/20/2017 🔍
06/20/2017 🔍
10/19/2019 🔍
Sources
Advisory: duo.comStatus: Not defined
CVE: CVE-2017-3215 (🔍)
GCVE (CVE): GCVE-0-2017-3215
GCVE (VulDB): GCVE-100-102692
scip Labs: https://www.scip.ch/en/?labs.20130704
See also: 🔍
Entry
Created: 06/20/2017 11:50Updated: 10/19/2019 09:56
Changes: 06/20/2017 11:50 (58), 10/19/2019 09:56 (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.