CVE-2019-0657 — Microsoft.NETCore.App
MEDIUMCVE-2019-0657 is a medium-severity (CVSS 5.9) Improper Input Validation vulnerability in Microsoft.NETCore.App. A fix is available for Microsoft.NETCore.App — see the affected versions and patch details below.
Improper Input Validation in .Net Framework API's
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2019-0657 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
Microsoft.NETCore.App.NETMicrosoft.NETCore.App.NETSystem.Private.UriReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.
Description
A vulnerability exists in certain .Net Framework API's and Visual Studio in the way they parse URL's, aka '.NET Framework and Visual Studio Spoofing Vulnerability'.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| .NETNuGet | Microsoft.NETCore.App | ≥ 2.2.0&&< 2.2.2 | 2.2.2dotnet add package Microsoft.NETCore.App --version 2.2.2 |
| .NETNuGet | Microsoft.NETCore.App | ≥ 2.1.0&&< 2.1.8 | 2.1.8dotnet add package Microsoft.NETCore.App --version 2.1.8 |
| .NETNuGet | System.Private.Uri | ≥ 4.3.0&&< 4.3.2 | 4.3.2dotnet add package System.Private.Uri --version 4.3.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Microsoft.NETCore.App, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update Microsoft.NETCore.App to 2.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-0657 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2019-0657 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2019-0657. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| .NET Core on Red Hat Enterprise Linux | rh-dotnet21-0:2.1-7.el7 | RHSA-2019:0349 |
Frequently Asked Questions
Is CVE-2019-0657 in your dependencies?
O3 Security finds CVE-2019-0657 across NuGet dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.