# CVE-2019-17087: Path traversal in AcuToWeb

> Attackers can enumerate and download arbitrary files from the server filesystem via an unauthorized file download vulnerability in Micro Focus AcuToWeb.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Dec 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-pf85-3hgc-m9ph

## What is CVE-2019-17087?

CVE-2019-17087 is a high-severity path traversal vulnerability in Micro Focus International AcuToWeb, published on 11 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unauthorized file download vulnerability in all supported versions of Micro Focus AcuToWeb. The vulnerability could be exploited to enumerate and download files from the filesystem of the system running AcuToWeb, with the privileges of the account AcuToWeb is running under.

## Which versions are affected by CVE-2019-17087?

It affects 1 product.


Products: Microfocus Acutoweb.

## How do I fix CVE-2019-17087?

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

## Is CVE-2019-17087 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-17087 and fix it if it is affected.

What it is: CVE-2019-17087 is a high-severity path traversal vulnerability in Micro Focus International AcuToWeb, published on 11 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-17087 in the wild and no public exploit code.

Affected product: Micro Focus International AcuToWeb. 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-2019-17087/ (Markdown: https://insights.sbomify.com/CVE-2019-17087/index.md)
```

## Sources

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

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