# CVE-2017-5219: Path traversal in n/a

> Attackers can upload a crafted zip file to traverse directories and install a web shell, achieving remote code execution with SYSTEM privileges.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Feb 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-9h7v-mvfw-jj5x

## What is CVE-2017-5219?

CVE-2017-5219 is a critical path traversal vulnerability in n/a, published on 2 Feb 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in SageCRM 7.x before 7.3 SP3. The Component Manager functionality, provided by SageCRM, permits additional components to be added to the application to enhance provided functionality. This functionality allows a zip file to be uploaded, containing a valid .ecf component file, which will be extracted to the inf directory outside of the webroot. By creating a zip file containing an empty .ecf file, to pass file-validation checks, any other file provided in zip file will be extracted onto the filesystem. In this case, a web shell with the filename '..\WWWRoot\CustomPages\aspshell.asp' was included within the zip file that, when extracted, traversed back out of the inf directory and into the SageCRM webroot. This permitted remote interaction with the underlying filesystem with the highest privilege level, SYSTEM.

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

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

It affects 1 product.


Products: Sagecrm Sagecrm.

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

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

## Is CVE-2017-5219 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-5218](https://insights.sbomify.com/CVE-2017-5218/): SQL injection in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-5219 is a critical path traversal vulnerability in n/a, published on 2 Feb 2017. 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-2017-5219 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-2017-5219/ (Markdown: https://insights.sbomify.com/CVE-2017-5219/index.md)
```

## Sources

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

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