Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Microsoft Security Advisory CVE-2019-1075: ASP.NET Core Spoofing Vulnerability #12007

Closed
blowdart opened this issue Jul 9, 2019 · 6 comments
Closed

Microsoft Security Advisory CVE-2019-1075: ASP.NET Core Spoofing Vulnerability #12007

blowdart opened this issue Jul 9, 2019 · 6 comments
Labels
area-networking Includes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions Security
Milestone
Discussions

Comments

@blowdart
Copy link
Contributor

blowdart commented Jul 9, 2019

Microsoft Security Advisory CVE-2019-1075: ASP.NET Core Spoofing Vulnerability

Executive summary

Microsoft is releasing this security advisory to provide information about a vulnerability in ASP.NET Core 2.1 and 2.2. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.

Microsoft is aware of a spoofing vulnerability that exists in ASP.NET Core that could lead to an open redirect. An attacker who successfully exploited the vulnerability could redirect a targeted user to a malicious website.

To exploit the vulnerability, an attacker could send a link that has a specially crafted URL and convince the user to click the link.

The update addresses the vulnerability by correcting how ASP.NET Core parses URLs.

Original Announcement

The original announcement for this issue can be found at aspnet/Announcements#373

Mitigation factors

Microsoft has not identified any mitigating factors for this vulnerability.

Affected software

Any ASP.NET Core based application that uses any of following vulnerable packages:

Package name Vulnerable versions Secure versions
Microsoft.AspNetCore.Server.HttpSys 2.1.0, 2.1.1
2.2.0		 2.1.12
2.2.6
Microsoft.AspNetCore.Server.IIS 2.2.0, 2.2.1, 2.2.2 2.2.6
Microsoft.AspNetCore.All 2.1.0 - 2.1.11
2.2.0 - 2.2.5		 2.1.12
2.2.6
Microsoft.AspNetCore.App 2.1.0 - 2.1.11
2.2.0 - 2.2.5		 2.1.12
2.2.6

Advisory FAQ

How do I know if I am affected?

The affected assemblies are part of .NET Core. If you are running a vulnerable version of .NET Core you may be affected.

How do I fix the issue?

To fix the issue please install the latest version of .NET Core. If you have multiple versions of .NET Core installed you will need to install multiple runtimes, or SDKs depending on what you have installed.

If you have .NET Core 2.0 or greater installed, you can list the versions you have installed by running the dotnet --info command. You will see output like the following;

.NET Core SDK (reflecting any global.json):
 Version:   3.0.100-preview3-010431
 Commit:    d72abce213

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.18362
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\3.0.100-preview3-010431\

Host (useful for support):
  Version: 3.0.0-preview3-27503-5
  Commit:  3844df9537

.NET Core SDKs installed:
  2.1.604 [C:\Program Files\dotnet\sdk]
  2.2.202 [C:\Program Files\dotnet\sdk]
  3.0.100-preview3-010431 [C:\Program Files\dotnet\sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.All 2.1.11 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]\
  Microsoft.AspNetCore.All 2.2.3 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.11 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.2.3 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.0.0-preview3-19153-02 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.1.11 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.2.3 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.0.0-preview3-27503-5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 3.0.0-preview3-27504-2 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

To install additional .NET Core runtimes or SDKs:
  https://aka.ms/dotnet-download

If you have both 2.1 and 2.2, you need to install updates for both versions.

Once you have installed the updated runtime or SDK, restart your apps for the update to take effect.

If you have pinned your application to a specific version of the runtime, you must update your app, recompile and redeploy it for the update to take effect.

Other Information

Reporting Security Issues

If you have found a potential security issue in .NET Core, please email details to secure@microsoft.com. Reports may qualify for the .NET Core Bug Bounty. Details of the .NET Core Bug Bounty including terms and conditions are at https://aka.ms/corebounty.

Support

You can ask questions about this issue on GitHub in the .NET Core or ASP.NET Core organizations. These are located at https://github.com/dotnet/ and https://github.com/aspnet/, respectively. The Announcements repo for each product (https://github.com/dotnet/Announcements and https://github.com/aspnet/Announcements) will contain this bulletin as an issue and will include a link to a discussion issue. You can ask questions in the discussion issue.

Disclaimer

The information provided in this advisory is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.

Acknowledgements

Reported through Datalust

External Links

CVE-2019-1075

Revisions

V1.0 (July 9, 2019): Advisory published.

Version 1.0

Last Updated 2019-07-09
@blowdart blowdart added the area-auth Includes: Authn, Authz, OAuth, OIDC, Bearer label Jul 9, 2019
@blowdart blowdart mentioned this issue Jul 9, 2019
Open
@corneliutusnea
Copy link

How does this apply to Azure WebApps? What is the recommended way to protect an app running on Azure WebApp. The latest runtime I see installed is 2.2.5.

@blowdart
Copy link
Contributor Author

The way Azure web apps proxies requests is different to how IIS and Windows hosting does it, and the issue shouldn't arise.

@fadamsen
Copy link

@blowdart If that is the case, could you update the advisory to include this as a mitigating factor?

@blowdart
Copy link
Contributor Author

I'll do some more investigation first to be 100% sure.

@markusschaber
Copy link

markusschaber commented Jul 11, 2019 •
edited

Is there any information whether Kestrel in ASP.NET Core 2.1 hosted behind reverse proxies like NginX or AWS ALB affected (on Linux, no Windows/IIS)?

I'm also a bit unsure how to understand CVE-2019-1075 in general.
My interpretation is that an attacker could craft an URL which points to https://my-asp.server/some/tricky/url/from/bad/guy, and when the victim clicks on that link (assuming it's for my-asp.sever), my server (running ASP.NET Core) redirects the http request to some bad guys site via http redirect?
So the core problem seems that the ASP.NET infrastructure can be tricked into generating redirects, instead of regular processing of the request, right?

@analogrelay analogrelay added this to the Discussions milestone Jul 11, 2019
@analogrelay analogrelay added area-servers Security and removed area-auth Includes: Authn, Authz, OAuth, OIDC, Bearer labels Jul 11, 2019
@ghost
Copy link

ghost commented Nov 12, 2020

Thank you for contacting us. Due to a lack of activity on this discussion issue we're closing it in an effort to keep our backlog clean. If you believe there is a concern related to the ASP.NET Core framework, which hasn't been addressed yet, please file a new issue.

This issue will be locked after 30 more days of inactivity. If you still wish to discuss this subject after then, please create a new issue!

@ghost ghost closed this as completed Nov 12, 2020
@dotnet dotnet locked as resolved and limited conversation to collaborators Dec 12, 2020
@amcasey amcasey added area-networking Includes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions and removed area-runtime labels Aug 24, 2023
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
area-networking Includes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions Security
Projects
None yet
Milestone
Discussions
Development

No branches or pull requests
6 participants
@analogrelay @corneliutusnea @blowdart @markusschaber @fadamsen @amcasey