# CVE-2017-2622: Information disclosure in openstack-mistral

> A malicious system user can access sensitive information from the OpenStack Workflow service due to improperly configured world-readable log directories.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 27 Jul 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-6vmp-9x58-mv62, RHSA-2017:1584, UBUNTU-CVE-2017-2622

## What is CVE-2017-2622?

CVE-2017-2622 is a medium-severity vulnerability in Redhat Openstack, published on 27 Jul 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), CWE-552 (Files or Directories Accessible to External Parties)

## Which versions are affected by CVE-2017-2622?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openstack-mistral` | Red Hat:openstack:10::el7 | All versions | 0:3.0.2-11.el7ost |
| `openstack-mistral-all` | Red Hat:openstack:10::el7 | All versions | 0:3.0.2-11.el7ost |
| `openstack-mistral-api` | Red Hat:openstack:10::el7 | All versions | 0:3.0.2-11.el7ost |
| `openstack-mistral-common` | Red Hat:openstack:10::el7 | All versions | 0:3.0.2-11.el7ost |
| `openstack-mistral-engine` | Red Hat:openstack:10::el7 | All versions | 0:3.0.2-11.el7ost |
| `openstack-mistral-executor` | Red Hat:openstack:10::el7 | All versions | 0:3.0.2-11.el7ost |
| `python-mistral-tests` | Red Hat:openstack:10::el7 | All versions | 0:3.0.2-11.el7ost |
| `python-openstack-mistral` | Red Hat:openstack:10::el7 | All versions | 0:3.0.2-11.el7ost |

Products: Redhat Openstack.

## How do I fix CVE-2017-2622?

Apply the vendor's patch.

## Is CVE-2017-2622 being exploited?

There is no known exploitation of CVE-2017-2622 in the wild and no public exploit code.

## Other vulnerabilities in Redhat Openstack

- [CVE-2015-1842](https://insights.sbomify.com/CVE-2015-1842/): Hardcoded credentials in n/a (critical 10.0)
- [CVE-2017-2637](https://insights.sbomify.com/CVE-2017-2637/): Auth bypass in rhosp-director (critical 9.9)
- [CVE-2022-38065](https://insights.sbomify.com/CVE-2022-38065/): Privilege escalation in OpenStack (high 8.8)
- [CVE-2016-4474](https://insights.sbomify.com/CVE-2016-4474/): Hardcoded credentials in n/a (high 8.8)
- [CVE-2021-31918](https://insights.sbomify.com/CVE-2021-31918/): Information disclosure in tripleo-ansible (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-2622 and fix it if it is affected.

What it is: CVE-2017-2622 is a medium-severity vulnerability in Redhat Openstack, published on 27 Jul 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-2622 in the wild and no public exploit code.

Affected product: Redhat Openstack. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-2622/ (Markdown: https://insights.sbomify.com/CVE-2017-2622/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-2622
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-2622
- OSV: https://osv.dev/vulnerability/CVE-2017-2622

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-2622/
Summaries are generated and may contain mistakes; the official description above is the record.