Skip to content
Fencer Intel
medium 5.9

CVE-2019-0657 json

Improper Input Validation in .Net Framework API's

published 7y ago modified 4mo ago also GHSA-x5qj-9vmx-7g6g , EUVD-2022-5721

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

Summary

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

Patch / fix

  • nuget Microsoft.NETCore.App 2.1.8, 2.2.2
  • nuget System.Private.Uri 4.3.2
  • rh-dotnet21 RHEL 2.1 DOTNET 2.1-7.el7
  • rh-dotnet22 RHEL 2.2 DOTNET 2.2-3.el7
  • rh-dotnet21-dotnet RHEL 2.1 DOTNET 2.1.504-1.el7
  • rh-dotnet22-dotnet RHEL 2.2 DOTNET 2.2.104-2.el7
  • rh-dotnet21-runtime RHEL 2.1 DOTNET 2.1-7.el7
  • rh-dotnet22-runtime RHEL 2.2 DOTNET 2.2-3.el7
  • rh-dotnet21-dotnet-host RHEL 2.1 DOTNET 2.1.8-1.el7
  • rh-dotnet22-dotnet-host RHEL 2.2 DOTNET 2.2.2-2.el7

red hat advisories RHSA-2019:0349

Is CVE-2019-0657 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-2019-0657 updated cvss 7.5

dotnet: Domain-spoofing attack in System.Uri

  • Red Hat .NET Core 1.0 on Red Hat Enterprise Linux rh-dotnetcore10 Red Hat .NET Core 1.1 on Red Hat Enterprise Linux rh-dotnetcore11
    affected: no fix planned “Will not fix”
  • Red Hat .NET Core on Red Hat Enterprise Linux ComputeNode (v. 7) rh-dotnet21 2.1-7.el7, rh-dotnet22 2.2-3.el7, rh-dotnet21-runtime 2.1-7.el7, rh-dotnet22-runtime 2.2-3.el7, rh-dotnet21-dotnet 2.1.504-1.el7, rh-dotnet22-dotnet 2.2.104-2.el7, +11 more Red Hat .NET Core on Red Hat Enterprise Linux Server (v. 7) rh-dotnet21 2.1-7.el7, rh-dotnet22 2.2-3.el7, rh-dotnet21-runtime 2.1-7.el7, rh-dotnet22-runtime 2.2-3.el7, rh-dotnet21-dotnet 2.1.504-1.el7, rh-dotnet22-dotnet 2.2.104-2.el7, +11 more Red Hat .NET Core on Red Hat Enterprise Linux Workstation (v. 7) rh-dotnet21 2.1-7.el7, rh-dotnet22 2.2-3.el7, rh-dotnet21-runtime 2.1-7.el7, rh-dotnet22-runtime 2.2-3.el7, rh-dotnet21-dotnet 2.1.504-1.el7, rh-dotnet22-dotnet 2.2.104-2.el7, +11 more
    fixed: vendor fix RHSA-2019:0349
  • Red Hat Enterprise Linux 8 dotnet, dotnet-host, dotnet-sdk-2.1, dotnet-runtime-2.1, dotnet-sdk-2.1.5xx, dotnet-host-fxr-2.1
    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

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
nuget Microsoft.NETCore.App
>=2.2.0, <2.2.2
>=2.1.0, <2.1.8
2.2.2
2.1.8
nuget System.Private.Uri
>=4.3.0, <4.3.2
4.3.2

Affected products

  • Microsoft Microsoft .NET Framework 4.5.2
  • Microsoft Microsoft .NET Framework 4.6
  • Microsoft .NET Core
  • Microsoft Microsoft Visual Studio
  • Microsoft Microsoft .NET Framework 4.7.2
  • Microsoft Microsoft .NET Framework 4.6/4.6.1/4.6.2
  • Microsoft Microsoft .NET Framework 4.6/4.6.1/4.6.2/4.7/4.7.1/4.7.2
  • Microsoft Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2
  • Microsoft Microsoft .NET Framework 4.7/4.7.1/4.7.2
  • Microsoft Microsoft .NET Framework 4.7.1/4.7.2
  • Microsoft PowerShell Core
  • Microsoft Microsoft Visual Studio 2017
  • Microsoft Microsoft .NET Framework 3.5
  • Microsoft Microsoft .NET Framework 3.0
  • Microsoft Microsoft .NET Framework 2.0
  • Microsoft Microsoft .NET Framework 3.5.1

Classification

Weakness
  • CWE-20 Improper Input Validation

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.