# CVE-2019-9632: Path traversal in n/a

> An attacker can download arbitrary files from the ESAFENET CDG server by manipulating the fileName parameter in a specific request.

- **Severity:** High 7.5 (`CVSS:3.0/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:** 8 Mar 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-j8x4-532w-f4xq

## What is CVE-2019-9632?

CVE-2019-9632 is a high-severity path traversal vulnerability in n/a, published on 8 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ESAFENET CDG V3 and V5 has an arbitrary file download vulnerability via the fileName parameter in download.jsp because the InstallationPack parameter is mishandled in a /CDGServer3/ClientAjax request.

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

It affects 1 product.


Products: Esafenet Electronic Document Security Management System.

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

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

## Is CVE-2019-9632 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-9632 exists.

Public exploit code:

- ESAFENET CDG - Arbitrary File Download (nuclei): http/cves/2019/CVE-2019-9632.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2019-9632 is a high-severity path traversal vulnerability in n/a, published on 8 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-9632 exists.

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-2019-9632/ (Markdown: https://insights.sbomify.com/CVE-2019-9632/index.md)
```

## Sources

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

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