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

Published: 2019-03-05 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]

NVD Status：Modified，CVE State: published

View at NVD, CVE.org, EUVD

Threat Intelligence & Risk Assessment for CVE-2019-0657

EPSS CVSS CWE GHSA Affected OS Tracker

Conclusion & alert: CVE-2019-0657 is rated Moderate Risk (51.7/100): CVSS Medium severity, with high exploitation likelihood (EPSS 4.52%, 90th percentile). Core evidence: EPSS ranks this CVE among the most likely to be exploited in the near term. Mandatory action: High exploitation likelihood—assess exposure and prioritize remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2019-0657

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	8.02%	4.52%	-3.50%
2	2026-02-28	4.80%	8.02%	+3.21%
3	2026-02-04	—	4.80%	—

Full EPSS history (26 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2019-0657

CVSS metrics for this CVE.

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
5.9	3.0	MEDIUM	`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:H) Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:N) Service keeps running; no real outage angle.	2.2	3.6	[email protected]
4.3	2.0	MEDIUM	`AV:N/AC:M/Au:N/C:N/I:P/A:N` Click to expand Access vector (AV:N) Can be exploited remotely over network reachability. Access complexity (AC:M) Exploitation needs some favorable conditions, but not exceptional ones. Authentication (AU:N) No authentication is required. Confidentiality impact (C:N) No confidentiality impact. Integrity impact (I:P) Partial integrity impact. Availability impact (A:N) No availability impact.	8.6	2.9	[email protected]

Weakness enumeration for CVE-2019-0657

CWE-20 MITRE ↗

GitHub Security Advisory for CVE-2019-0657

GHSA-x5qj-9vmx-7g6g · Severity: medium · Ecosystem: nuget — Improper Input Validation in .Net Framework API's

OS Trackers for CVE-2019-0657

vendor	priority	summary	link
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2019-0657

Affected software / configurations for CVE-2019-0657

Vendor	Product	Version	Raw CPE
microsoft	.net_core	1.0	cpe:2.3:a:microsoft:.net_core:1.0:::::::*
microsoft	.net_core	2.1	cpe:2.3:a:microsoft:.net_core:2.1:::::::*
microsoft	.net_core	2.2	cpe:2.3:a:microsoft:.net_core:2.2:::::::*
microsoft	powershell_core	6.0	cpe:2.3:a:microsoft:powershell_core:6.0:::::::*
microsoft	powershell_core	6.1	cpe:2.3:a:microsoft:powershell_core:6.1:::::::*
microsoft	visual_studio_2017	—	cpe:2.3:a:microsoft:visual_studio_2017:-:::::::*
microsoft	visual_studio_2017	15.9	cpe:2.3:a:microsoft:visual_studio_2017:15.9:::::::*
microsoft	.net_framework	2.0	cpe:2.3:a:microsoft:.net_framework:2.0:sp2::::::
microsoft	.net_framework	3.0	cpe:2.3:a:microsoft:.net_framework:3.0:sp2::::::
microsoft	.net_framework	3.5	cpe:2.3:a:microsoft:.net_framework:3.5:::::::*
microsoft	.net_framework	3.5.1	cpe:2.3:a:microsoft:.net_framework:3.5.1:::::::*
microsoft	.net_framework	4.5.2	cpe:2.3:a:microsoft:.net_framework:4.5.2:::::::*
microsoft	.net_framework	4.6	cpe:2.3:a:microsoft:.net_framework:4.6:::::::*
microsoft	.net_framework	4.6.2	cpe:2.3:a:microsoft:.net_framework:4.6.2:::::::*
microsoft	.net_framework	4.7	cpe:2.3:a:microsoft:.net_framework:4.7:::::::*
microsoft	.net_framework	4.7.1	cpe:2.3:a:microsoft:.net_framework:4.7.1:::::::*
microsoft	.net_framework	4.7.2	cpe:2.3:a:microsoft:.net_framework:4.7.2:::::::*
microsoft	.net_framework	4.6.1	cpe:2.3:a:microsoft:.net_framework:4.6.1:::::::*

References for CVE-2019-0657

URL	Tags
http://www.securityfocus.com/bid/106890	Third Party Advisory VDB Entry
https://access.redhat.com/errata/RHSA-2019:0349	Third Party Advisory
https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0657	Patch Vendor Advisory

cvelogic Threat Intelligence