Skip to content
Fencer Intel
medium 5.5

CVE-2019-1142 json

An elevation of privilege vulnerability exists when the .NET Framework common language runtime (CLR) allows file creation in arbitrary loca…

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

cvss
5.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.0%
EPSS 1.0% chance of exploitation in 30 days, percentile 64%
public exploits
0
none known

Summary

An elevation of privilege vulnerability exists when the .NET Framework common language runtime (CLR) allows file creation in arbitrary locations, aka '.NET Framework Elevation of Privilege Vulnerability'.

Patch / fix

Is CVE-2019-1142 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

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

CVSS scores

assigned by version score vector
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
NVD 2.0 2.1 AV:L/AC:L/Au:N/C:N/I:P/A:N

Affected products

  • Microsoft Microsoft .NET Framework 4.5.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.8 on Windows Server 2012
  • Microsoft Microsoft .NET Framework 4.8 on Windows Server 2012 (Server Core installation)
  • Microsoft Microsoft .NET Framework 4.8 on Windows 8.1 for 32-bit systems
  • Microsoft Microsoft .NET Framework 4.8 on Windows 8.1 for x64-based systems
  • Microsoft Microsoft .NET Framework 4.8 on Windows Server 2012 R2
  • Microsoft Microsoft .NET Framework 4.8 on Windows RT 8.1
  • Microsoft Microsoft .NET Framework 4.8 on Windows Server 2012 R2 (Server Core installation)
  • Microsoft Microsoft .NET Framework 4.8 on Windows Server 2016
  • Microsoft Microsoft .NET Framework 4.8 on Windows 10 Version 1607 for 32-bit Systems
  • Microsoft Microsoft .NET Framework 4.8 on Windows 10 Version 1607 for x64-based Systems
  • Microsoft Microsoft .NET Framework 4.8 on Windows Server 2016 (Server Core installation)
  • Microsoft Microsoft .NET Framework 4.8 on Windows 10 Version 1703 for 32-bit Systems
  • Microsoft Microsoft .NET Framework 4.8 on Windows 10 Version 1703 for x64-based Systems
  • Microsoft Microsoft .NET Framework 4.8 on Windows 10 Version 1709 for 32-bit Systems
  • Microsoft Microsoft .NET Framework 4.8 on Windows 10 Version 1709 for x64-based Systems
  • Microsoft Microsoft .NET Framework 4.8 on Windows 10 Version 1803 for 32-bit Systems
  • Microsoft Microsoft .NET Framework 4.8 on Windows 10 Version 1803 for x64-based Systems
  • Microsoft Microsoft .NET Framework 4.8 on Windows Server, version 1803 (Server Core Installation)
  • Microsoft Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 1809 for 32-bit Systems
  • Microsoft Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 1809 for x64-based Systems
  • Microsoft Microsoft .NET Framework 3.5 AND 4.8 on Windows Server 2019
  • Microsoft Microsoft .NET Framework 3.5 AND 4.8 on Windows Server 2019 (Server Core installation)
  • Microsoft Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 1903 for 32-bit Systems
  • Microsoft Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 1903 for x64-based Systems
  • Microsoft Microsoft .NET Framework 3.5 AND 4.8 on Windows Server, version 1903 (Server Core installation)
  • Microsoft Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 Version 1809 for 32-bit Systems
  • Microsoft Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 Version 1809 for x64-based Systems
  • Microsoft Microsoft .NET Framework 3.5 AND 4.7.2 on Windows Server 2019
  • Microsoft Microsoft .NET Framework 3.5 AND 4.7.2 on Windows Server 2019 (Server Core installation)
  • Microsoft Microsoft .NET Framework 3.5

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

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.