OpenStack Workflow Service Log Directory information disclosure
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
4.9 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in OpenStack Workflow. Affected by this issue is some unknown functionality of the component Service Log Directory. The manipulation leads to information disclosure. This vulnerability is handled as CVE-2017-2622. An attack has to be approached locally. There is no exploit available. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Details
A vulnerability classified as problematic was found in OpenStack Workflow (Cloud Software) (version now known). Affected by this vulnerability is some unknown processing of the component Service Log Directory. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. The summary by CVE is:
An accessibility flaw was found in the OpenStack Workflow (mistral) service where a service log directory was improperly made world readable. A malicious system user could exploit this flaw to access sensitive information.
The bug was discovered 06/28/2017. The weakness was published 07/27/2018 as not defined bug report (Bugzilla). It is possible to read the advisory at bugzilla.redhat.com. This vulnerability is known as CVE-2017-2622 since 11/30/2016. Attacking locally is a requirement. Required for exploitation is a single authentication. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.
The vulnerability was handled as a non-public zero-day exploit for at least 394 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.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.9VulDB Meta Temp Score: 4.9
VulDB Base Score: 3.3
VulDB Temp Score: 3.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
NVD Vector: 🔍
CNA Base Score: 5.9
CNA Vector (Red Hat, Inc.): 🔍
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: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
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
11/30/2016 🔍06/28/2017 🔍
07/27/2018 🔍
07/27/2018 🔍
07/28/2018 🔍
04/27/2023 🔍
Sources
Vendor: openstack.orgAdvisory: RHSA-2017:1584
Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-2622 (🔍)
GCVE (CVE): GCVE-0-2017-2622
GCVE (VulDB): GCVE-100-122275
Entry
Created: 07/28/2018 07:34 AMUpdated: 04/27/2023 11:38 AM
Changes: 07/28/2018 07:34 AM (57), 03/10/2020 08:39 PM (2), 04/27/2023 11:30 AM (3), 04/27/2023 11:38 AM (12)
Complete: 🔍
Cache ID: 18:4E9:40
No comments yet. Languages: en.
Please log in to comment.