[Security] Bump Microsoft.AspNetCore.All from 2.0.0 to 2.2.2

[dependabot-preview]

Bumps Microsoft.AspNetCore.All from 2.0.0 to 2.2.2. This update includes security fixes.

Vulnerabilities fixed

Sourced from The Sonatype OSS Index.

[CVE-2018-0875] Improper Input Validation
.NET Core 1.0, .NET Core 1.1, NET Core 2.0 and PowerShell Core 6.0.0 allow a denial of Service vulnerability due to how specially crafted requests are handled, aka ".NET Core Denial of Service Vulnerability".

Affected versions: 1.0.0; 1.1.0; 2.0.0

Sourced from The Sonatype OSS Index.

[CVE-2017-8700] ASP.NET Core 1.0, 1.1, and 2.0 allow an attacker to bypass Cross-origin Resource...
ASP.NET Core 1.0, 1.1, and 2.0 allow an attacker to bypass Cross-origin Resource Sharing (CORS) configurations and retrieve normally restricted content from a web application, aka "ASP.NET Core Information Disclosure Vulnerability".

Affected versions: 1.0.0; 1.1.0; 2.0.0

Sourced from The Sonatype OSS Index.

[CVE-2018-0784] Permissions, Privileges, and Access Controls
ASP.NET Core 1.0. 1.1, and 2.0 allow an elevation of privilege vulnerability due to the ASP.NET Core project templates, aka "ASP.NET Core Elevation Of Privilege Vulnerability". This CVE is unique from CVE-2018-0808.

Affected versions: 2.0.0

Sourced from The Sonatype OSS Index.

[CVE-2018-0786] Microsoft .NET Framework 1.1, 2.0, 3.0, 3.5, 3.5.1, 4, 4.5, 4.5.1, 4.5.2, 4.6, 4...
Microsoft .NET Framework 1.1, 2.0, 3.0, 3.5, 3.5.1, 4, 4.5, 4.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, and 4.7 and .NET Core 1.0 and 2.0 allow a security feature bypass vulnerability due to the way certificates are validated, aka ".NET Security Feature Bypass Vulnerability".

Affected versions: 1.0.0; 2.0.0

Sourced from The Sonatype OSS Index.

[CVE-2017-11883] .NET Core 1.0, 1.1, and 2.0 allow an unauthenticated attacker to remotely cause ...
.NET Core 1.0, 1.1, and 2.0 allow an unauthenticated attacker to remotely cause a denial of service attack against a .NET Core web application by improperly handling web requests, aka ".NET CORE Denial Of Service Vulnerability".

Affected versions: 1.0.0; 1.1.0; 2.0.0

Sourced from The Sonatype OSS Index.

[CVE-2018-0787] Weak Password Recovery Mechanism for Forgotten Password
ASP.NET Core 1.0. 1.1, and 2.0 allow an elevation of privilege vulnerability due to how web applications that are created from templates validate web requests, aka "ASP.NET Core Elevation Of Privilege Vulnerability".

Affected versions: 1.0.0; 1.1.0; 2.0.0

Sourced from The Sonatype OSS Index.

[CVE-2017-11879] ASP.NET Core 2.0 allows an attacker to steal log-in session information such as ...
ASP.NET Core 2.0 allows an attacker to steal log-in session information such as cookies or authentication tokens via a specially crafted URL aka "ASP.NET Core Elevation Of Privilege Vulnerability".

Affected versions: 2.0.0

Sourced from The Sonatype OSS Index.

[CVE-2018-0808] Permissions, Privileges, and Access Controls
ASP.NET Core 1.0. 1.1, and 2.0 allow an elevation of privilege vulnerability due to how ASP.NET web applications handle web requests, aka "ASP.NET Core Elevation Of Privilege Vulnerability". This CVE is unique from CVE-2018-0784.

Affected versions: 1.0.0; 1.1.0; 2.0.0

Sourced from The Sonatype OSS Index.

[CVE-2018-0764] Data Handling
Microsoft .NET Framework 1.1, 2.0, 3.0, 3.5, 3.5.1, 4, 4.5, 4.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2 and 5.7 and .NET Core 1.0. 1.1 and 2.0 allow a denial of service vulnerability due to the way XML documents are processed, aka ".NET and .NET Core Denial Of Service Vulnerability". This CVE is unique from CVE-2018-0765.

Affected versions: 1.0.0; 1.1.0; 2.0.0

Sourced from The Sonatype OSS Index.

[CVE-2017-11770] .NET Core 1.0, 1.1, and 2.0 allow an unauthenticated attacker to remotely cause ...
.NET Core 1.0, 1.1, and 2.0 allow an unauthenticated attacker to remotely cause a denial of service attack against a .NET Core web application by improperly parsing certificate data. A denial of service vulnerability exists when .NET Core improperly handles parsing certificate data, aka ".NET CORE Denial Of Service Vulnerability".

Affected versions: 1.0.0; 1.1.0; 2.0.0

Sourced from The Sonatype OSS Index.

[CVE-2018-0785] Cross-Site Request Forgery (CSRF)
ASP.NET Core 1.0. 1.1, and 2.0 allow a cross site request forgery vulnerability due to the ASP.NET Core project templates, aka "ASP.NET Core Cross Site Request Forgery Vulnerability".

Affected versions: 2.0.0

Sourced from The Sonatype OSS Index.

[CVE-2018-0765] Improper Restriction of XML External Entity Reference ("XXE")
A denial of service vulnerability exists when .NET and .NET Core improperly process XML documents, aka ".NET and .NET Core Denial of Service Vulnerability." This affects Microsoft .NET Framework 2.0, Microsoft .NET Framework 3.0, Microsoft .NET Framework 4.7.1, Microsoft .NET Framework 4.6/4.6.1/4.6.2/4.7/4.7.1, Microsoft .NET Framework 4.5.2, Microsoft .NET Framework 4.7/4.7.1, Microsoft .NET Framework 4.6, Microsoft .NET Framework 3.5, Microsoft .NET Framework 3.5.1, Microsoft .NET Framework 4.6/4.6.1/4.6.2, Microsoft .NET Framework 4.6.2/4.7/4.7.1, .NET Core 2.0, Microsoft .NET Framework 4.7.2.

Affected versions: 2.0.0

Sourced from The GitHub Security Advisory Database.

Moderate severity vulnerability that affects Microsoft.AspNetCore.Server.Kestrel.Core, Microsoft.AspNetCore.Server.Kestrel.Transport.Abstractions, Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv, and Microsoft.AspNetCore.All
Microsoft made an internal discovery of a security vulnerability in version 2.x of ASP.NET Core where
a specially crafted request can cause excess resource consumption in Kestrel.

Affected versions: >= 2.0.0, <= 2.0.7

Sourced from The GitHub Security Advisory Database.

Moderate severity vulnerability that affects Microsoft.AspNetCore.Server.Kestrel.Core, Microsoft.AspNetCore.All, and Microsoft.AspNetCore.App
Microsoft is aware of a denial of service vulnerability in ASP.NET Core when a malformed request is terminated. An attacker who successfully exploited this vulnerability could cause a denial of service attack.

The update addresses the vulnerability by correcting how ASP.NET Core handles such requests.

Affected versions: >= 2.0.0, <= 2.0.8

Release notes

Sourced from Microsoft.AspNetCore.All's releases.

v2.2.2

No release notes provided.

ASP.NET Core 2.2.1

• Release Notes
• Download and Install

Repos

• CoreCLR
• CoreFX
• Core-Setup
• CLI
• ASP

ASP.NET Core 2.2.0

• General Release Notes
• Download and Install

ASP.NET Core release notes

We have disabled view recompilation when .cshtml change by default (except for the Development environment). A new flag called AllowRecompilingViewsOnFileChange has been introduced in RazorViewEngineOptions, which can be used to configure whether the view engine will watch for file changes. The settings is set to false by default for all environments but Development. If you are using Visual Studio to debug, then it will launch the application in the Development environment by default. You can find more details about the change by looking at this PR: https://github-redirect.dependabot.com/aspnet/Mvc/pull/8369/files

In case you would like to keep the view recompilation enabled for your project, you can choose so by configure Razor options in Startup.ConfigureService method using the following code block:

services.AddMvc()
    .SetCompatibilityVersion(CompatibilityVersion.Version_2_2)
    .AddRazorOptions(options => options.AllowRecompilingViewsOnFileChange = true);

Repos

• CoreCLR
• CoreFX
• Core-Setup
• CLI
• ASP.NET
• EF

2.2.0-preview3

Known issues: https://github-redirect.dependabot.com/aspnet/Announcements/issues/323

2.2.0-preview2

ASP.NET Core 2.2.0-preview2

For more details, see the blog post here: https://blogs.msdn.microsoft.com/webdev/2018/09/12/asp-net-core-2-2-0-preview2-now-available.

To see all issues closed in the 2.2.0 Preview 2 milestone, see the results of this query.

2.2.0-preview1

ASP.NET Core 2.2.0 Preview 1 Release Notes

We are pleased to announce the release of ASP.NET Core 2.2.0 Preview 1.

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge
• @dependabot reopen will reopen this PR if it is closed
• @dependabot ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

Finally, you can contact us by mentioning @dependabot.

[dependabot-preview]

Superseded by #24.