# CVE-2019-1075: Open redirect in ASP.NET Core > An open redirect vulnerability in ASP.NET Core allows attackers to spoof URLs, potentially leading to phishing attacks. - **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 15 Jul 2019 - **Updated:** 4 Aug 2024 - **Also known as:** GHSA-prrf-397v-83xh ## What is CVE-2019-1075? CVE-2019-1075 is a medium-severity vulnerability in Microsoft ASP.NET Core, published on 15 Jul 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description A spoofing vulnerability exists in ASP.NET Core that could lead to an open redirect, aka 'ASP.NET Core Spoofing Vulnerability'. Weakness: CWE-601 (URL Redirection to Untrusted Site) ## Which versions are affected by CVE-2019-1075? 14 open source packages ship an affected version, including Microsoft.AspNetCore.All, Microsoft.AspNetCore.App and Microsoft.AspNetCore.Server.HttpSys. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `Microsoft.AspNetCore.All` | NuGet | From 2.1.0 | 2.1.12 | | `Microsoft.AspNetCore.All` | NuGet | From 2.1.0 | 2.1.12 | | `Microsoft.AspNetCore.All` | NuGet | From 2.2.0 | 2.2.6 | | `Microsoft.AspNetCore.All` | NuGet | From 2.2.0 | 2.2.6 | | `Microsoft.AspNetCore.App` | NuGet | From 2.1.0 | 2.1.12 | | `Microsoft.AspNetCore.App` | NuGet | From 2.1.0 | 2.1.12 | | `Microsoft.AspNetCore.App` | NuGet | From 2.2.0 | 2.2.6 | | `Microsoft.AspNetCore.App` | NuGet | From 2.2.0 | 2.2.6 | | `Microsoft.AspNetCore.Server.HttpSys` | NuGet | From 2.1.0 | 2.1.12 | | `Microsoft.AspNetCore.Server.HttpSys` | NuGet | From 2.1.0 | 2.1.12 | | `Microsoft.AspNetCore.Server.HttpSys` | NuGet | From 2.2.0 | 2.2.6 | | `Microsoft.AspNetCore.Server.HttpSys` | NuGet | From 2.2.0 | 2.2.6 | | `Microsoft.AspNetCore.Server.IIS` | NuGet | From 2.2.0 | 2.2.6 | | `Microsoft.AspNetCore.Server.IIS` | NuGet | From 2.2.0 | 2.2.6 | Products: Microsoft Asp.net Core. ## How do I fix CVE-2019-1075? Upgrade Microsoft.AspNetCore.All to a fixed version for your release line: 2.1.12 or 2.2.6. ## Is CVE-2019-1075 being exploited? There is no known exploitation of CVE-2019-1075 in the wild and no public exploit code. ## Other vulnerabilities in Microsoft ASP.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-2019-1075 and fix it if it is affected. What it is: CVE-2019-1075 is a medium-severity vulnerability in Microsoft ASP.NET Core, published on 15 Jul 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2019-1075 in the wild and no public exploit code. Affected packages and fixed versions: - Microsoft.AspNetCore.All (NuGet): affected from 2.1.0; fixed in 2.1.12 - Microsoft.AspNetCore.All (NuGet): affected from 2.1.0; fixed in 2.1.12 - Microsoft.AspNetCore.All (NuGet): affected from 2.2.0; fixed in 2.2.6 - Microsoft.AspNetCore.All (NuGet): affected from 2.2.0; fixed in 2.2.6 - Microsoft.AspNetCore.App (NuGet): affected from 2.1.0; fixed in 2.1.12 - Microsoft.AspNetCore.App (NuGet): affected from 2.1.0; fixed in 2.1.12 - Microsoft.AspNetCore.App (NuGet): affected from 2.2.0; fixed in 2.2.6 - Microsoft.AspNetCore.App (NuGet): affected from 2.2.0; fixed in 2.2.6 - Microsoft.AspNetCore.Server.HttpSys (NuGet): affected from 2.1.0; fixed in 2.1.12 - Microsoft.AspNetCore.Server.HttpSys (NuGet): affected from 2.1.0; fixed in 2.1.12 - Microsoft.AspNetCore.Server.HttpSys (NuGet): affected from 2.2.0; fixed in 2.2.6 - Microsoft.AspNetCore.Server.HttpSys (NuGet): affected from 2.2.0; fixed in 2.2.6 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-1075/ (Markdown: https://insights.sbomify.com/CVE-2019-1075/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-1075 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-1075 - OSV: https://osv.dev/vulnerability/CVE-2019-1075 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-1075/ Summaries are generated and may contain mistakes; the official description above is the record.