# CVE-2021-32017: Information disclosure in n/a

> A JUMP AMS SOAP endpoint allows attackers to list the remote file system structure, exposing directory and file names.

- **Severity:** Critical 9.9 (`CVSS:3.1/AC:L/AV:N/A:H/C:H/I:H/PR:L/S:C/UI: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:** 3 Aug 2021
- **Updated:** 30 May 2025
- **Also known as:** GHSA-rjw6-fhxf-vxvf

## What is CVE-2021-32017?

CVE-2021-32017 is a critical vulnerability in n/a, published on 3 Aug 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in JUMP AMS 3.6.0.04.009-2487. A JUMP SOAP endpoint permitted the listing of the content of the remote file system. This can be used to identify the complete server filesystem structure, i.e., identifying all the directories and files.

## Which versions are affected by CVE-2021-32017?

It affects 1 product.


Products: Jump-Technology Asset Management.

## How do I fix CVE-2021-32017?

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

## Is CVE-2021-32017 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-32016](https://insights.sbomify.com/CVE-2021-32016/): Path traversal in n/a (critical 9.9)
- [CVE-2021-32018](https://insights.sbomify.com/CVE-2021-32018/): Path traversal in n/a (high 8.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-32017 and fix it if it is affected.

What it is: CVE-2021-32017 is a critical vulnerability in n/a, published on 3 Aug 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-32017 in the wild and no public exploit code.

Affected product: n/a. 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-2021-32017/ (Markdown: https://insights.sbomify.com/CVE-2021-32017/index.md)
```

## Sources

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

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