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

> An attacker can craft a restore request to write files to unauthorized locations, leading to privilege escalation and data modification.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Aug 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-5pj4-43hp-78xf

## What is CVE-2019-11551?

CVE-2019-11551 is a medium-severity path traversal vulnerability in n/a, published on 21 Aug 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In Code42 Enterprise and Crashplan for Small Business through Client version 6.9.1, an attacker can craft a restore request to restore a file through the Code42 app to a location they do not have privileges to write.

Weakness: CWE-269 (Improper Privilege Management)

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

It affects 2 products.


Products: Code42 Code42 for Enterprise, Code42 Crashplan for Small Business.

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

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

## Is CVE-2019-11551 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-11552](https://insights.sbomify.com/CVE-2019-11552/): Code injection in n/a (high 7.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-11551 is a medium-severity path traversal vulnerability in n/a, published on 21 Aug 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-11551 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-2019-11551/ (Markdown: https://insights.sbomify.com/CVE-2019-11551/index.md)
```

## Sources

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

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