Skip to content
Fencer Intel
high 7.5

CVE-2017-8700 in the critical feed json

Cross-origin Resource Sharing bypass in ASP.NET Core

published 2017-11-15 8 y ago modified 2026-06-17 4 mo ago also GHSA-3rp6-rjw4-cq39 , EUVD-2022-2236

cvss
7.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
10.4%
EPSS 10.4% chance of exploitation in 30 days, percentile 95%
public exploits
0
none known

Summary

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

Patch / fix

  • nuget Microsoft.AspNetCore.Mvc.Core 1.0.6, 1.1.6
  • nuget Microsoft.AspNetCore.Mvc.Cors 1.0.6, 1.1.6

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-8700 updated cvss 8.7

ASP.NET: CORS not properly applied

  • Red Hat .NET Core 1.0 on Red Hat Enterprise Linux rh-dotnetcore10-dotnetcore Red Hat .NET Core 1.1 on Red Hat Enterprise Linux rh-dotnetcore11-dotnetcore Red Hat .NET Core 2.0 on Red Hat Enterprise Linux rh-dotnet20-dotnet
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

10.36% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N
GitHub 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
nuget Microsoft.AspNetCore.Mvc.Core
>=1.0.0, <1.0.6
>=1.1.0, <1.1.6
1.0.6
1.1.6
nuget Microsoft.AspNetCore.Mvc.Cors
>=1.0.0, <1.0.6
>=1.1.0, <1.1.6
1.0.6
1.1.6

Affected products

  • Microsoft Corporation ASP.NET Core

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.