# CVE-2019-0976: NuGet Package Manager Tampering Vulnerability

> An authenticated attacker can tamper with intermediate build files in the NuGet Package Manager for Linux and Mac.

- **Severity:** Medium 5.5 (`CVSS:3.1/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:** Yes
- **Published:** 16 May 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-3hcm-6fjc-47qq

## What is CVE-2019-0976?

CVE-2019-0976 is a medium-severity missing authorization vulnerability in Microsoft Nuget, published on 16 May 2019. It can only be exploited from the same machine or local 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 contents of the intermediate build folder (by default "obj"), aka 'NuGet Package Manager Tampering Vulnerability'.

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

2 open source packages ship an affected version, including NuGet.Commands. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `NuGet.Commands` | NuGet | From 5.0.0 | 5.0.2 |
| `NuGet.Commands` | NuGet | From 5.0.0 | 5.0.2 |

Products: Microsoft Nuget.

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

Upgrade NuGet.Commands to 5.0.2 or later.

## Is CVE-2019-0976 being exploited?

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

## Other vulnerabilities in Microsoft Nuget

- [CVE-2023-29337](https://insights.sbomify.com/CVE-2023-29337/): NuGet Client Remote Code Execution Vulnerability (high 7.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-0976 is a medium-severity missing authorization vulnerability in Microsoft Nuget, published on 16 May 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-0976 in the wild and no public exploit code.

Affected packages and fixed versions:
- NuGet.Commands (NuGet): affected from 5.0.0; fixed in 5.0.2
- NuGet.Commands (NuGet): affected from 5.0.0; fixed in 5.0.2

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

## Sources

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

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