# CVE-2018-8292: .NET Core Information Disclosure

> Attackers can obtain authentication information via exposed redirects in .NET Core and PowerShell Core, requiring a security patch.

- **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:** 10 Oct 2018
- **Updated:** 5 Aug 2024
- **Also known as:** ECHO-a484-b54c-511d, GHSA-7jgj-8wvc-jh57, RHSA-2018:2902

## What is CVE-2018-8292?

CVE-2018-8292 is a high-severity vulnerability in Microsoft .NET Core, published on 10 Oct 2018. 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 Core when authentication information is inadvertently exposed in a redirect, aka ".NET Core Information Disclosure Vulnerability." This affects .NET Core 2.1, .NET Core 1.0, .NET Core 1.1, PowerShell Core 6.0.

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

## Which versions are affected by CVE-2018-8292?

2 open source packages ship an affected version, including System.Net.Http. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `System.Net.Http` | NuGet | All versions | 4.3.4 |
| `System.Net.Http` | NuGet | All versions | 4.3.4 |
| `rh-dotnetcore10-dotnetcore` | Red Hat:rhel_dotnet:1.0::el7 | All versions | 0:1.0.13-1.el7 |
| `rh-dotnetcore10-dotnetcore-debuginfo` | Red Hat:rhel_dotnet:1.0::el7 | All versions | 0:1.0.13-1.el7 |
| `rh-dotnetcore11-dotnetcore` | Red Hat:rhel_dotnet:1.1::el7 | All versions | 0:1.1.10-1.el7 |
| `rh-dotnetcore11-dotnetcore-debuginfo` | Red Hat:rhel_dotnet:1.1::el7 | All versions | 0:1.1.10-1.el7 |

Products: Microsoft Asp.net Core, Microsoft Powershell Core.

## How do I fix CVE-2018-8292?

Upgrade System.Net.Http to 4.3.4 or later.

## Is CVE-2018-8292 being exploited?

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

## Other vulnerabilities in Microsoft .NET Core

- [CVE-2025-55315](https://insights.sbomify.com/CVE-2025-55315/): ASP.NET Security Feature Bypass Vulnerability (critical 9.9)
- [CVE-2026-88092](https://insights.sbomify.com/CVE-2026-88092/): ASP.NET Core Tampering Vulnerability (critical 9.4)
- [CVE-2026-40372](https://insights.sbomify.com/CVE-2026-40372/): ASP.NET Core Elevation of Privilege Vulnerability (critical 9.1)
- [CVE-2021-43877](https://insights.sbomify.com/CVE-2021-43877/): ASP.NET Core and Visual Studio Elevation of Privilege Vulnerability (high 8.8)
- [CVE-2020-0603](https://insights.sbomify.com/CVE-2020-0603/): Remote code execution in ASP.NET Core (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-8292 and fix it if it is affected.

What it is: CVE-2018-8292 is a high-severity vulnerability in Microsoft .NET Core, published on 10 Oct 2018. 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-2018-8292 in the wild and no public exploit code.

Affected packages and fixed versions:
- System.Net.Http (NuGet): affected all versions; fixed in 4.3.4
- System.Net.Http (NuGet): affected all versions; fixed in 4.3.4

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

## Sources

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

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