Skip to content
Fencer Intel
medium 5.5

CVE-2019-0864 json

A denial of service vulnerability exists when .NET Framework improperly handles objects in heap memory, aka '.NET Framework Denial of Servi…

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

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

Summary

A denial of service vulnerability exists when .NET Framework improperly handles objects in heap memory, aka '.NET Framework Denial of Service Vulnerability'.

Patch / fix

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

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-0864 updated cvss 4.3

dotnet: improper handling of objects in heap memory causing denial of service

  • Red Hat .NET Core 1.0 on Red Hat Enterprise Linux rh-dotnetcore10-dotnetcore Red Hat .NET Core 1.1 on Red Hat Enterprise Linux rh-dotnetcore11-dotnetcore Red Hat .NET Core 2.1 on Red Hat Enterprise Linux rh-dotnet21, rh-dotnet21-runtime Red Hat .NET Core 2.2 on Red Hat Enterprise Linux rh-dotnet22, rh-dotnet22-runtime 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

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

CVSS scores

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

Affected products

  • Microsoft Microsoft .NET Framework 4.5.2
  • Microsoft Microsoft .NET Framework 4.6
  • Microsoft Microsoft .NET Framework 4.6.2 on Windows 10 for 32-bit Systems
  • Microsoft Microsoft .NET Framework 4.6.2 on Windows 10 for x64-based Systems
  • Microsoft Microsoft .NET Framework 4.7.2
  • Microsoft Microsoft .NET Framework 4.7.2 on Windows 10 Version 1809 for ARM64-based Systems
  • 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 .NET Framework 4.8 on Windows 7 for 32-bit Systems Service Pack 1
  • Microsoft Microsoft .NET Framework 4.8 on Windows 7 for x64-based Systems Service Pack 1
  • Microsoft Microsoft .NET Framework 4.8 on Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation)
  • Microsoft Microsoft .NET Framework 4.8 on Windows Server 2008 R2 for x64-based Systems Service Pack 1
  • 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 4.8 on Windows 10 Version 1809 for 32-bit Systems
  • Microsoft Microsoft .NET Framework 4.8 on Windows 10 Version 1809 for x64-based Systems
  • Microsoft Microsoft .NET Framework 4.8 on Windows Server 2019
  • Microsoft Microsoft .NET Framework 4.8 on Windows Server 2019 (Server Core installation)
  • Microsoft Microsoft .NET Framework 4.8 on Windows 10 Version 1903 for 32-bit Systems
  • Microsoft Microsoft .NET Framework 4.8 on Windows 10 Version 1903 for x64-based Systems
  • Microsoft Microsoft .NET Framework 4.8 on Windows Server, version 1903 (Server Core installation)
  • Microsoft Microsoft .NET Framework 3.5
  • Microsoft Microsoft .NET Framework 3.5 on Windows 10 Version 1903 for 32-bit Systems
  • Microsoft Microsoft .NET Framework 3.5 on Windows 10 Version 1903 for x64-based Systems
  • Microsoft Microsoft .NET Framework 3.5 on Windows Server, version 1903 (Server Core installation)
  • Microsoft Microsoft .NET Framework 3.0
  • Microsoft Microsoft .NET Framework 2.0
  • Microsoft Microsoft .NET Framework 3.5.1

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.