Skip to content
Fencer Intel
high 8.8

CVE-2019-0613 in the critical feed json

A remote code execution vulnerability exists in .NET Framework and Visual Studio software when the software fails to check the source marku…

published 7y ago modified 4mo ago also EUVD-2019-1377

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

Summary

A remote code execution vulnerability exists in .NET Framework and Visual Studio software when the software fails to check the source markup of a file.An attacker who successfully exploited the vulnerability could run arbitrary code in the context of the current user, aka '.NET Framework and Visual Studio Remote Code Execution Vulnerability'.

Patch / fix

Is CVE-2019-0613 in your stack? 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

Exploit prediction

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

CVSS scores

assigned by version score vector
NVD 3.0 8.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 9.3 AV:N/AC:M/Au:N/C:C/I:C/A:C

Affected products

  • Microsoft Microsoft .NET Framework 4.5.2
  • Microsoft Microsoft .NET Framework 4.6
  • 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 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-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

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.