Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5

Cookie parsing failure

CVE-2020-1045GHSA-hxrm-9w7p-39cc

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (microsoft.aspnetcore.app.runtime.linux-arm64 3.1.8; microsoft.aspnetcore.app.runtime.linux-musl-arm64 3.1.8; microsoft.owin 4.1.1; microsoft.aspnetcore.app.runtime.osx-x64 3.1.8; microsoft.aspnetcore.app.runtime.linux-arm 3.1.8; 8 more packages under Affected packages), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

  • GitHub Advisory Database and maintainer security advisories on GitHub

    GitHub-reviewed advisory GHSA-hxrm-9w7p-39cc lists affected ranges: NuGet microsoft.aspnetcore.app >=0 =0 =3.1.0 =3.1.0 =3.1.0 =3.1.0 =3.1.0 <3.1.8; NuGet…

    VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
EPSS
  • CVE-2020-1045: 5.93% estimated exploitation activity in the next 30 days; percentile 93.26 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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'.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-hxrm-9w7p-39cc

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2020-1045

Advisory: Cookie parsing failure
IDs: CVE-2020-1045, GHSA-hxrm-9w7p-39cc
Record: https://patchnext.com/advisories/cve-2020-1045 (revision 1, source checked 26 Oct 2026, 17:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: microsoft.aspnetcore.app.runtime.linux-arm64 3.1.8; microsoft.aspnetcore.app.runtime.linux-musl-arm64 3.1.8; microsoft.owin 4.1.1; microsoft.aspnetcore.app.runtime.osx-x64 3.1.8; microsoft.aspnetcore.app.runtime.linux-arm 3.1.8; microsoft.aspnetcore.app.runtime.win-x86 3.1.8; microsoft.aspnetcore.app.runtime.linux-x64 3.1.8; microsoft.aspnetcore.app.runtime.win-arm 3.1.8; microsoft.aspnetcore.app.runtime.linux-musl-x64 3.1.8; microsoft.aspnetcore.app.runtime.win-x64 3.1.8; microsoft.aspnetcore.app 2.1.22; microsoft.aspnetcore.http 2.1.22; microsoft.aspnetcore.app.runtime.win-arm64 3.1.8. A vendor fix does not mean a deployment is fixed.

## Affected components
- NuGet microsoft.aspnetcore.app.runtime.linux-arm64: affected >= 3.1.0, < 3.1.8; fixed in 3.1.8
- NuGet microsoft.aspnetcore.app.runtime.linux-musl-arm64: affected >= 3.1.0, < 3.1.8; fixed in 3.1.8
- NuGet microsoft.owin: affected < 4.1.1; fixed in 4.1.1
- NuGet microsoft.aspnetcore.app.runtime.osx-x64: affected >= 3.1.0, < 3.1.8; fixed in 3.1.8
- NuGet microsoft.aspnetcore.app.runtime.linux-arm: affected >= 3.1.0, < 3.1.8; fixed in 3.1.8
- NuGet microsoft.aspnetcore.app.runtime.win-x86: affected >= 3.1.0, < 3.1.8; fixed in 3.1.8
- NuGet microsoft.aspnetcore.app.runtime.linux-x64: affected >= 3.1.0, < 3.1.8; fixed in 3.1.8
- NuGet microsoft.aspnetcore.app.runtime.win-arm: affected >= 3.1.0, < 3.1.8; fixed in 3.1.8
- NuGet microsoft.aspnetcore.app.runtime.linux-musl-x64: affected >= 3.1.0, < 3.1.8; fixed in 3.1.8
- NuGet microsoft.aspnetcore.app.runtime.win-x64: affected >= 3.1.0, < 3.1.8; fixed in 3.1.8
- NuGet microsoft.aspnetcore.app: affected <= 2.1.21; fixed in 2.1.22
- NuGet microsoft.aspnetcore.http: affected < 2.1.22; fixed in 2.1.22
- NuGet microsoft.aspnetcore.app.runtime.win-arm64: affected >= 3.1.5, < 3.1.8; fixed in 3.1.8

## Suggested inspection (read-only)
- NuGet microsoft.aspnetcore.app.runtime.linux-arm64: check the installed version with your package manager.
- NuGet microsoft.aspnetcore.app.runtime.linux-musl-arm64: check the installed version with your package manager.
- NuGet microsoft.owin: check the installed version with your package manager.
- NuGet microsoft.aspnetcore.app.runtime.osx-x64: check the installed version with your package manager.
- NuGet microsoft.aspnetcore.app.runtime.linux-arm: check the installed version with your package manager.
- NuGet microsoft.aspnetcore.app.runtime.win-x86: check the installed version with your package manager.
- NuGet microsoft.aspnetcore.app.runtime.linux-x64: check the installed version with your package manager.
- NuGet microsoft.aspnetcore.app.runtime.win-arm: check the installed version with your package manager.
- NuGet microsoft.aspnetcore.app.runtime.linux-musl-x64: check the installed version with your package manager.
- NuGet microsoft.aspnetcore.app.runtime.win-x64: check the installed version with your package manager.
- NuGet microsoft.aspnetcore.app: check the installed version with your package manager.
- NuGet microsoft.aspnetcore.http: check the installed version with your package manager.
- NuGet microsoft.aspnetcore.app.runtime.win-arm64: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on microsoft.aspnetcore.app.runtime.linux-arm64, microsoft.aspnetcore.app.runtime.linux-musl-arm64, microsoft.owin, microsoft.aspnetcore.app.runtime.osx-x64, microsoft.aspnetcore.app.runtime.linux-arm, microsoft.aspnetcore.app.runtime.win-x86, microsoft.aspnetcore.app.runtime.linux-x64, microsoft.aspnetcore.app.runtime.win-arm, microsoft.aspnetcore.app.runtime.linux-musl-x64, microsoft.aspnetcore.app.runtime.win-x64, microsoft.aspnetcore.app, microsoft.aspnetcore.http, microsoft.aspnetcore.app.runtime.win-arm64.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-hxrm-9w7p-39cc (GitHub-reviewed advisory GHSA-hxrm-9w7p-39cc lists affected ranges: NuGet microsoft.aspnetcore.app >=0 =0 =3.1.0 =3.1.0 =3.1.0 =3.1.0 =3.1.0 <3.1.8; NuGet…)

Commands are suggestions: review each one before running it.

Loading voting…