LiveActive security incident?Get immediate response
CVE Record

CVE-2020-1045: Microsoft ASP.NET Core Security Feature Bypass Vulnerability

<p>A security feature bypass vulnerability exists in the way Microsoft ASP.NET Core parses encoded cookie names.</p> <p>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.</p> <p>The security update addresses the vulnerability by fixing the way the ASP.NET Core cookie parser handles encoded names.</p>

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2020-1045 is a security feature bypass in Microsoft ASP.NET Core cookie parsing. An attacker could exploit percent-encoded cookie names to create a second cookie that the application may interpret incorrectly. The main business risk is unauthorized manipulation of application state or security decisions, not data theft or service outage.

Executive priority

Treat this as a high-priority patching item for exposed ASP.NET Core applications. The risk is integrity compromise through security bypass, with remote unauthenticated reach, but available evidence does not confirm active exploitation.

Technical view

ASP.NET Core decoded entire cookie strings instead of safely handling encoded cookie names. This could allow duplicate logical cookie names, including one percent encoded, leading to integrity-impacting security bypass. The CVSS 3.1 score is 7.5, with network attack vector, low complexity, no privileges, no user interaction, and high integrity impact.

Likely exposure

Exposure is most likely in applications running affected ASP.NET Core 2.1 or 3.1 components that accept browser or API cookies from untrusted clients. Internet-facing apps, authentication flows, session handling, and middleware relying on cookie names deserve priority review.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. The CVSS vector includes proof-of-concept exploit maturity, but no cited source here confirms active in-the-wild exploitation.

Researcher notes

Focus analysis on cookie-name canonicalization and middleware assumptions around duplicate or encoded cookie names. Do not assume confidentiality or availability impact from the provided CVSS; the stated impact is integrity high, confidentiality none, availability none.

Mitigation direction

  • Apply Microsoft security updates for affected ASP.NET Core versions.
  • Update Fedora or Red Hat .NET packages using the cited vendor advisories.
  • Inventory containers, hosts, and build images for affected ASP.NET Core runtimes.
  • Check MSRC and vendor advisories for exact fixed package versions.
  • Regression test authentication and session flows after updating.

Validation and detection

  • Identify ASP.NET Core runtime and package versions across production assets.
  • Check dependency manifests, container images, and host runtimes for affected versions.
  • Confirm installed packages match Microsoft, Fedora, or Red Hat fixed releases.
  • Review internet-facing apps that depend on cookie-based security decisions.
  • Verify cookie parsing behavior through safe regression tests only.
Prepared
Confidence
high
Sources
8

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2020-1045 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N/E:P/RL:O/RC:C

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
7Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N/E:P/RL:O/RC:C3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2020-1045Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N/E:P/RL:O/RC:C

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MicrosoftASP.NET Core 2.12.0Listed
MicrosoftASP.NET Core 3.13.0Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.