# CVE-2017-2627: Path traversal in openstack-tripleo-common

> Permissive sudoers configuration allows directory traversal and grants root access to the validations user, enabling privilege escalation in OpenStack environments.

- **Severity:** High 8.2 (`CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Aug 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-mqhr-f34x-gw3r

## What is CVE-2017-2627?

CVE-2017-2627 is a high-severity path traversal vulnerability in Redhat Openstack, published on 22 Aug 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A flaw was found in openstack-tripleo-common as shipped with Red Hat Openstack Enterprise 10 and 11. The sudoers file as installed with OSP's openstack-tripleo-common package is much too permissive. It contains several lines for the mistral user that have wildcards that allow directory traversal with '..' and it grants full passwordless root access to the validations user.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 2 products.


Products: Openstack Tripleo-Common, Redhat Openstack.

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

No fix has been published for CVE-2017-2627 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-2627 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-2627 is a high-severity path traversal vulnerability in Redhat Openstack, published on 22 Aug 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-2627 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-2627/ (Markdown: https://insights.sbomify.com/CVE-2017-2627/index.md)
```

## Sources

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

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