# CVE-2019-3737: Dell EMC Avamar Security Update for ADMe Web UI Vulnerability

> A malicious user can download arbitrary files from the Dell EMC Avamar ADMe Web Interface via a specially crafted request.

- **Severity:** High 8.6 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/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:** 19 Jun 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-p4r9-w473-78rf

## What is CVE-2019-3737?

CVE-2019-3737 is a high-severity path traversal vulnerability in Dell EMC Avamar, published on 19 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Dell EMC Avamar ADMe Web Interface 1.0.50 and 1.0.51 are affected by an LFI vulnerability which may allow a malicious user to download arbitrary files from the affected system by sending a specially crafted request to the Web Interface application.

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

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

It affects 1 product.


Products: Dell Avamar Data Migration Enabler Web Interface.

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

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

## Is CVE-2019-3737 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-3737 is a high-severity path traversal vulnerability in Dell EMC Avamar, published on 19 Jun 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-3737 in the wild and no public exploit code.

Affected product: Dell EMC Avamar. 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-3737/ (Markdown: https://insights.sbomify.com/CVE-2019-3737/index.md)
```

## Sources

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

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