# CVE-2019-0757: Path traversal in .NET Core SDK

> An authenticated attacker can tamper with NuGet package folder structures, potentially altering package contents or behavior.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Apr 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-c2wg-p84q-4x76, RHSA-2019:0544

## What is CVE-2019-0757?

CVE-2019-0757 is a medium-severity path traversal vulnerability in Microsoft Visual Studio 2017, published on 9 Apr 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A tampering vulnerability exists in the NuGet Package Manager for Linux and Mac that could allow an authenticated attacker to modify a NuGet package's folder structure, aka 'NuGet Package Manager Tampering Vulnerability'.

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

It affects 8 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rh-dotnetcore10-dotnetcore` | Red Hat:rhel_dotnet:1.0::el7 | All versions | 0:1.0.15-1.el7 |
| `rh-dotnetcore10-dotnetcore-debuginfo` | Red Hat:rhel_dotnet:1.0::el7 | All versions | 0:1.0.15-1.el7 |
| `rh-dotnetcore11-dotnetcore` | Red Hat:rhel_dotnet:1.1::el7 | All versions | 0:1.1.12-1.el7 |
| `rh-dotnetcore11-dotnetcore-debuginfo` | Red Hat:rhel_dotnet:1.1::el7 | All versions | 0:1.1.12-1.el7 |
| `rh-dotnet21` | Red Hat:rhel_dotnet:2.1::el7 | All versions | 0:2.1-8.el7 |
| `rh-dotnet21-dotnet` | Red Hat:rhel_dotnet:2.1::el7 | All versions | 0:2.1.505-1.el7 |
| `rh-dotnet21-dotnet-debuginfo` | Red Hat:rhel_dotnet:2.1::el7 | All versions | 0:2.1.505-1.el7 |
| `rh-dotnet21-dotnet-host` | Red Hat:rhel_dotnet:2.1::el7 | All versions | 0:2.1.9-1.el7 |
| `rh-dotnet21-dotnet-runtime-2.1` | Red Hat:rhel_dotnet:2.1::el7 | All versions | 0:2.1.9-1.el7 |
| `rh-dotnet21-dotnet-sdk-2.1` | Red Hat:rhel_dotnet:2.1::el7 | All versions | 0:2.1.505-1.el7 |
| `rh-dotnet21-dotnet-sdk-2.1.5xx` | Red Hat:rhel_dotnet:2.1::el7 | All versions | 0:2.1.505-1.el7 |
| `rh-dotnet21-runtime` | Red Hat:rhel_dotnet:2.1::el7 | All versions | 0:2.1-8.el7 |
| `rh-dotnet22` | Red Hat:rhel_dotnet:2.2::el7 | All versions | 0:2.2-4.el7 |
| `rh-dotnet22-dotnet` | Red Hat:rhel_dotnet:2.2::el7 | All versions | 0:2.2.105-1.el7 |
| `rh-dotnet22-dotnet-debuginfo` | Red Hat:rhel_dotnet:2.2::el7 | All versions | 0:2.2.105-1.el7 |
| `rh-dotnet22-dotnet-host` | Red Hat:rhel_dotnet:2.2::el7 | All versions | 0:2.2.3-1.el7 |
| `rh-dotnet22-dotnet-host-fxr-2.2` | Red Hat:rhel_dotnet:2.2::el7 | All versions | 0:2.2.3-1.el7 |
| `rh-dotnet22-dotnet-runtime-2.2` | Red Hat:rhel_dotnet:2.2::el7 | All versions | 0:2.2.3-1.el7 |
| `rh-dotnet22-dotnet-sdk-2.2` | Red Hat:rhel_dotnet:2.2::el7 | All versions | 0:2.2.105-1.el7 |
| `rh-dotnet22-dotnet-sdk-2.2.1xx` | Red Hat:rhel_dotnet:2.2::el7 | All versions | 0:2.2.105-1.el7 |
| `rh-dotnet22-runtime` | Red Hat:rhel_dotnet:2.2::el7 | All versions | 0:2.2-4.el7 |

Products: Microsoft .Net Core Sdk, Microsoft Nuget, Microsoft Visual Studio 2017, Mono-Project Mono Framework, Redhat Enterprise Linux, Redhat Enterprise Linux Eus, Redhat Enterprise Linux Server Aus, Redhat Enterprise Linux Server Tus.

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

Apply the vendor's patch.

## Is CVE-2019-0757 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-0757 is a medium-severity path traversal vulnerability in Microsoft Visual Studio 2017, published on 9 Apr 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-0757 in the wild and no public exploit code.

Affected product: Microsoft Visual Studio 2017. 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-0757/ (Markdown: https://insights.sbomify.com/CVE-2019-0757/index.md)
```

## Sources

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

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