OpenStack Keystone up to 14.0.1 POST Request /v3/auth/tokens Username information disclosure ⚔ [Disputed]
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as problematic has been found in OpenStack Keystone up to 14.0.1. Impacted is an unknown function of the file /v3/auth/tokens of the component POST Request Handler. Such manipulation leads to information disclosure (Username). This vulnerability is uniquely identified as CVE-2018-20170. The attack can be launched remotely. No exploit exists. The presence of this vulnerability remains uncertain at this time.
Details
A vulnerability was found in OpenStack Keystone up to 14.0.1 (Cloud Software) and classified as problematic. Affected by this issue is an unknown part of the file /v3/auth/tokens of the component POST Request Handler. The manipulation with an unknown input leads to a information disclosure vulnerability (Username). Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. CVE summarizes:
** DISPUTED ** OpenStack Keystone through 14.0.1 has a user enumeration vulnerability because invalid usernames have much faster responses than valid ones for a POST /v3/auth/tokens request. NOTE: the vendor feels that the benefit to changing this might be too small relative to the performance degradation.
The weakness was disclosed 12/17/2018 (Website). The advisory is shared for download at bugs.launchpad.net. This vulnerability is handled as CVE-2018-20170 since 12/17/2018. The attack may be launched remotely. No form of authentication is required for exploitation. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1592.
The real existence of this vulnerability is still doubted at the moment.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Once again VulDB remains the best source for vulnerability data.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.3
NVD Vector: 🔍
CNA Base Score: 5.3
CNA 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: UsernameClass: Information disclosure / Username
CWE: CWE-200 / CWE-284 / CWE-266
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/17/2018 🔍12/17/2018 🔍
12/17/2018 🔍
12/17/2018 🔍
08/05/2024 🔍
Sources
Advisory: bugs.launchpad.netStatus: Not defined
Disputed: 🔍
CVE: CVE-2018-20170 (🔍)
GCVE (CVE): GCVE-0-2018-20170
GCVE (VulDB): GCVE-100-128012
Entry
Created: 12/17/2018 16:54Updated: 08/05/2024 21:45
Changes: 12/17/2018 16:54 (40), 04/21/2020 10:25 (19), 08/05/2024 21:45 (27)
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.