# CVE-2017-7433: Path traversal in Vibe

> Remote attackers can download arbitrary files from Micro Focus Vibe servers via path traversal in the viewFile endpoint.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 May 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-2hq2-g754-m7cw

## What is CVE-2017-7433?

CVE-2017-7433 is a medium-severity path traversal vulnerability in Micro Focus Vibe, published on 18 May 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An absolute path traversal vulnerability (CWE-36) in Micro Focus Vibe 4.0.2 and earlier allows a remote authenticated attacker to download arbitrary files from the server by submitting a specially crafted request to the viewFile endpoint. Note that the attack can be performed without authentication if Guest access is enabled (Guest access is disabled by default).

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

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

It affects 1 product.


Products: Micro Focus Vibe.

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

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

## Is CVE-2017-7433 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-7433 is a medium-severity path traversal vulnerability in Micro Focus Vibe, published on 18 May 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-7433 in the wild and no public exploit code.

Affected product: Micro Focus Vibe. 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-7433/ (Markdown: https://insights.sbomify.com/CVE-2017-7433/index.md)
```

## Sources

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

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