HighGHSA-hxrm-9w7p-39ccBIT-aspnet-core-2020-1045CVE-2020-1045

Cookie parsing failure

Published 24 May 2022 · Updated 29 Nov 2024

Is your project on an affected Microsoft.AspNetCore.Http?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
<2.1.22
Fixed in
2.1.22
Update to the fixed version for your release line, for example:dotnet add package Microsoft.AspNetCore.Http --version 2.1.22
Affected
<2.1.22
Fixed in
2.1.22
Update to the fixed version for your release line, for example:dotnet add package Microsoft.AspNetCore.App --version 2.1.22
Affected
<4.1.1
Fixed in
4.1.1
Update to the fixed version for your release line, for example:dotnet add package Microsoft.Owin --version 4.1.1
Affected
>=3.1.0 <3.1.8
Fixed in
3.1.8
Update to the fixed version for your release line, for example:dotnet add package Microsoft.AspNetCore.App.Runtime.linux-arm --version 3.1.8
Affected
>=3.1.0 <3.1.8
Fixed in
3.1.8
Update to the fixed version for your release line, for example:dotnet add package Microsoft.AspNetCore.App.Runtime.linux-arm64 --version 3.1.8
Affected
>=3.1.0 <3.1.8
Fixed in
3.1.8
Update to the fixed version for your release line, for example:dotnet add package Microsoft.AspNetCore.App.Runtime.linux-musl-x64 --version 3.1.8
Affected
>=3.1.0 <3.1.8
Fixed in
3.1.8
Update to the fixed version for your release line, for example:dotnet add package Microsoft.AspNetCore.App.Runtime.linux-x64 --version 3.1.8
Affected
>=3.1.0 <3.1.8
Fixed in
3.1.8
Update to the fixed version for your release line, for example:dotnet add package Microsoft.AspNetCore.App.Runtime.osx-x64 --version 3.1.8
Affected
>=3.1.0 <3.1.8
Fixed in
3.1.8
Update to the fixed version for your release line, for example:dotnet add package Microsoft.AspNetCore.App.Runtime.win-arm --version 3.1.8
Affected
>=3.1.0 <3.1.8
Fixed in
3.1.8
Update to the fixed version for your release line, for example:dotnet add package Microsoft.AspNetCore.App.Runtime.win-x64 --version 3.1.8
Affected
>=3.1.0 <3.1.8
Fixed in
3.1.8
Update to the fixed version for your release line, for example:dotnet add package Microsoft.AspNetCore.App.Runtime.win-x86 --version 3.1.8
Affected
>=3.1.0 <3.1.8
Fixed in
3.1.8
Update to the fixed version for your release line, for example:dotnet add package Microsoft.AspNetCore.App.Runtime.linux-musl-arm64 --version 3.1.8
Affected
>=3.1.5 <3.1.8
Fixed in
3.1.8
Update to the fixed version for your release line, for example:dotnet add package Microsoft.AspNetCore.App.Runtime.win-arm64 --version 3.1.8

Details

A security feature bypass vulnerability exists in the way Microsoft ASP.NET Core parses encoded cookie names.The ASP.NET Core cookie parser decodes entire cookie strings which could allow a malicious attacker to set a second cookie with the name being percent encoded.The security update addresses the vulnerability by fixing the way the ASP.NET Core cookie parser handles encoded names., aka 'Microsoft ASP.NET Core Security Feature Bypass Vulnerability'.

Is GHSA-hxrm-9w7p-39cc in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected Microsoft.AspNetCore.Http, and gives you the command that fixes it.

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.