Vulnerability · CVE-2017-8700
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 appl…
Published Nov 15, 2017 · catalog updated Jun 17, 2026 · asp.net core
Last checked Nov 8, 2026. A connected source was read within the last 7 days.
Check this week
CVE-2017-8700 is not in CISA KEV. FIRST estimates a 10.36% chance of exploitation in the next 30 days. Check whether you run asp.net core.
Gaps on this record
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
Same product and reporting
- CVE-2026-88092 · Critical
- CVE-2026-69304 · Medium
- CVE-2026-45591 · High
- CVE-2026-40372 · Critical
- CVE-2025-55315 · Critical
- Severity
- High7.5
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 10.36%
- Remediation
- Advisory link
- Affected products
- cpe microsoft/asp.net core
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".
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- cpe microsoft/asp.net core1.0
- cpe microsoft/asp.net core1.1
- cpe microsoft/asp.net core2.0
How to fix CVE-2017-8700
No stored fix
No vendor fix text is stored. Use the linked advisory before you change production.
Version check
Seen in 1.0 · 2 other packages on the advisory
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
CVE-2017-8700 is not in CISA KEV. FIRST estimates a 10.36% chance of exploitation in the next 30 days. Check whether you run asp.net core.
Which versions are affected?
Compare what you have installed with microsoft/asp.net core 1.0; microsoft/asp.net core 1.1; microsoft/asp.net core 2.0. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 10.36%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Technology hubs
Code
The project this record applies to. Exploit listings stay in References.
No public source repository is identified for this product.
Timeline
Detection, updates, and resolution for this record.
Nov 15, 2017 · Monitored products — high
Detected
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".
Jun 17, 2026 · Monitored products — high
Updated
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".
Sources
- CVE.orgVulnerability recordCVE-2017-8700
Official CVE identifier
cve.org - Monitored products — highVendor advisoryCVE-2017-8700
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".
nvd.nist.gov
References
Freshness
Last verified in this catalog Nov 8, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- CVE.orgNov 8, 2026
- Monitored products — highNov 8, 2026