Skip to content
Fencer Vulns
high 7.5

CVE-2019-1255 json

A denial of service vulnerability exists when Microsoft Defender improperly handles files, aka 'Microsoft Defender Denial of Service Vulner…

published 2019-09-23 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-9821

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

Summary

A denial of service vulnerability exists when Microsoft Defender improperly handles files, aka 'Microsoft Defender Denial of Service Vulnerability'.

Patch / fix

Exploit prediction

4.15% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

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

Affected products

  • Microsoft Microsoft Security Essentials
  • Microsoft Microsoft System Center
  • Microsoft Microsoft Forefront Endpoint Protection
  • Microsoft Windows Defender on Windows 7 for 32-bit Systems
  • Microsoft Windows Defender on Windows 7 for x64-based Systems
  • Microsoft Windows Defender on Windows Server 2008 R2 for x64-based Systems (Server Core installation)
  • Microsoft Windows Defender on Windows Server 2008 R2 for Itanium-Based Systems
  • Microsoft Windows Defender on Windows Server 2008 R2 for x64-based Systems
  • Microsoft Windows Defender on Windows Server 2008 for 32-bit Systems (Server Core installation)
  • Microsoft Windows Defender on Windows Server 2012
  • Microsoft Windows Defender on Windows Server 2012 (Server Core installation)
  • Microsoft Windows Defender on Windows 8.1 for 32-bit systems
  • Microsoft Windows Defender on Windows 8.1 for x64-based systems
  • Microsoft Windows Defender on Windows Server 2012 R2
  • Microsoft Windows Defender on Windows RT 8.1
  • Microsoft Windows Defender on Windows Server 2012 R2 (Server Core installation)
  • Microsoft Windows Defender on Windows 10 for 32-bit Systems
  • Microsoft Windows Defender on Windows 10 for x64-based Systems
  • Microsoft Windows Defender on Windows Server 2016
  • Microsoft Windows Defender on Windows 10 Version 1607 for 32-bit Systems
  • Microsoft Windows Defender on Windows 10 Version 1607 for x64-based Systems
  • Microsoft Windows Defender on Windows Server 2016 (Server Core installation)
  • Microsoft Windows Defender on Windows 10 Version 1703 for 32-bit Systems
  • Microsoft Windows Defender on Windows 10 Version 1703 for x64-based Systems
  • Microsoft Windows Defender on Windows 10 Version 1709 for 32-bit Systems
  • Microsoft Windows Defender on Windows 10 Version 1709 for x64-based Systems
  • Microsoft Windows Defender on Windows 10 Version 1803 for 32-bit Systems
  • Microsoft Windows Defender on Windows 10 Version 1803 for x64-based Systems
  • Microsoft Windows Defender on Windows Server, version 1803 (Server Core Installation)
  • Microsoft Windows Defender on Windows 10 Version 1803 for ARM64-based Systems
  • Microsoft Windows Defender on Windows 10 Version 1809 for 32-bit Systems
  • Microsoft Windows Defender on Windows 10 Version 1809 for x64-based Systems
  • Microsoft Windows Defender on Windows 10 Version 1809 for ARM64-based Systems
  • Microsoft Windows Defender on Windows Server 2019
  • Microsoft Windows Defender on Windows Server 2019 (Server Core installation)
  • Microsoft Windows Defender on Windows 10 Version 1709 for ARM64-based Systems
  • Microsoft Windows Defender on Windows 10 Version 1903 for 32-bit Systems
  • Microsoft Windows Defender on Windows 10 Version 1903 for x64-based Systems
  • Microsoft Windows Defender on Windows 10 Version 1903 for ARM64-based Systems
  • Microsoft Windows Defender on Windows Server, version 1903 (Server Core installation)
  • Microsoft Windows Defender on Windows Server 2008 for Itanium-Based Systems
  • Microsoft Windows Defender on Windows Server 2008 for 32-bit Systems

References

Sources

Fencer Vulns 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.