Microsoft.aspnetcore.mvc.cors vulnerabilitiesRanked by how likely they are to be used.
Microsoft.aspnetcore.mvc.cors is made by Microsoft. We track 3 published vulnerabilities in it, across 7 versions. None of them is on the list of flaws known to be exploited today. If you run Microsoft.aspnetcore.mvc.cors, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Microsoft.aspnetcore.mvc.cors vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Microsoft.aspnetcore.mvc.cors's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Microsoft.aspnetcore.mvc.cors flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 17%CVE-2017-0247High
A denial of service vulnerability exists when the ASP.NET Core fails to properly validate web requests.
- 4.2%CVE-2017-0249High
An elevation of privilege vulnerability exists when the ASP.NET Core fails to properly sanitize web requests.
- 3.5%CVE-2017-0256Medium
A spoofing vulnerability exists when the ASP.NET Core fails to properly sanitize web requests.
Running Microsoft.aspnetcore.mvc.cors? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
A denial of service vulnerability exists when the ASP.NET Core fails to properly validate web requests. NOTE: Microsoft has not commented on third-party claims that the issue is that the TextEncoder.EncodeCore function in the System.Text.Encodings.Web package in ASP.NET Core Mvc before 1.0.4 and 1.1.x before 1.1.3 allows remote attackers to cause a denial of service by leveraging failure to properly calculate the length of 4-byte characters in the Unicode Non-Character range.
- Matched to
- Microsoft.aspnetcore.mvc.cors on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 3 published vulnerabilities listed under the name Microsoft.aspnetcore.mvc.cors, across 7 versions.
None of Microsoft.aspnetcore.mvc.cors's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Microsoft.aspnetcore.mvc.cors. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.