# CVE-2019-0545: Exposure of Sensitive Information in System.Net.Http

> An information disclosure vulnerability in .NET Framework and Core allows bypassing CORS configurations, potentially exposing sensitive data to unauthorized origins.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/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:** Yes
- **Published:** 8 Jan 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-2xjx-v99w-gqf3

## What is CVE-2019-0545?

CVE-2019-0545 is a high-severity vulnerability in Microsoft .Net Framework, published on 8 Jan 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An information disclosure vulnerability exists in .NET Framework and .NET Core which allows bypassing Cross-origin Resource Sharing (CORS) configurations, aka ".NET Framework Information Disclosure Vulnerability." This affects Microsoft .NET Framework 2.0, Microsoft .NET Framework 3.0, Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2, Microsoft .NET Framework 4.5.2, Microsoft .NET Framework 4.6, Microsoft .NET Framework 4.6/4.6.1/4.6.2/4.7/4.7.1/4.7.2, Microsoft .NET Framework 4.7/4.7.1/4.7.2, .NET Core 2.1, Microsoft .NET Framework 4.7.1/4.7.2, Microsoft .NET Framework 3.5, Microsoft .NET Framework 3.5.1, Microsoft .NET Framework 4.6/4.6.1/4.6.2, .NET Core 2.2, Microsoft .NET Framework 4.7.2.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

4 open source packages ship an affected version, including Microsoft.NETCore.App. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `Microsoft.NETCore.App` | NuGet | From 2.1.0 | 2.1.7 |
| `Microsoft.NETCore.App` | NuGet | From 2.1.0 | 2.1.7 |
| `Microsoft.NETCore.App` | NuGet | From 2.2.0 | 2.2.1 |
| `Microsoft.NETCore.App` | NuGet | From 2.2.0 | 2.2.1 |

Products: Microsoft .Net Core, Microsoft .Net Framework.

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

Upgrade Microsoft.NETCore.App to a fixed version for your release line: 2.1.7 or 2.2.1.

## Is CVE-2019-0545 being exploited?

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

## Other vulnerabilities in Microsoft .Net Framework

- [CVE-2020-1147](https://insights.sbomify.com/CVE-2020-1147/): Microsoft .NET Framework, SharePoint, and Visual Studio Remote Code Execution (high 7.8, exploited in the wild)
- [CVE-2020-0605](https://insights.sbomify.com/CVE-2020-0605/): Code injection in .NET Core (high 8.8)
- [CVE-2020-0606](https://insights.sbomify.com/CVE-2020-0606/): Remote code execution in Microsoft.WindowsDesktop.App.Ref (high 8.8)
- [CVE-2019-1301](https://insights.sbomify.com/CVE-2019-1301/): High severity vulnerability that affects System.Management.Automation (high 7.5)
- [CVE-2019-0820](https://insights.sbomify.com/CVE-2019-0820/): Regular Expression Denial of Service in System.Text.RegularExpressions (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-0545 is a high-severity vulnerability in Microsoft .Net Framework, published on 8 Jan 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-0545 in the wild and no public exploit code.

Affected packages and fixed versions:
- Microsoft.NETCore.App (NuGet): affected from 2.1.0; fixed in 2.1.7
- Microsoft.NETCore.App (NuGet): affected from 2.1.0; fixed in 2.1.7
- Microsoft.NETCore.App (NuGet): affected from 2.2.0; fixed in 2.2.1
- Microsoft.NETCore.App (NuGet): affected from 2.2.0; fixed in 2.2.1

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

## Sources

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

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