CVE-2017-8558 in the critical feed json
The Microsoft Malware Protection Engine running on Microsoft Forefront and Microsoft Defender on 32-bit versions of Microsoft Windows Serve…
published 2017-06-29 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-17508
- cvss
- 7.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 43.6%
- EPSS 43.6% chance of exploitation in 30 days, percentile 98%
- public exploits
- 1
- Exploit-DB
Summary
The Microsoft Malware Protection Engine running on Microsoft Forefront and Microsoft Defender on 32-bit versions of Microsoft Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8.1, Windows Server 2012 Gold and R2, Windows RT 8.1, Windows 10 Gold, 1511, 1607, and 1703 does not properly scan a specially crafted file leading to memory corruption. aka "Microsoft Malware Protection Engine Remote Code Execution Vulnerability".
Timeline
- First public exploit (EDB-42264)
- Published
Exploit prediction
43.59% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-42264 Microsoft MsMpEng - mpengine x86 Emulator Heap Corruption in VFS API dos, 2017-06-27
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.8 | CVSS:3.0/AV:L/AC:L/PR:L/UI:N/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 Corporation Microsoft Malware Protection Engine
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
exploit-db.com
/exploits/42264/
exploit, third-party-advisory, vdb-entry
-
portal.msrc.microsoft.com
/en-US/security-guidance/advisory/CVE-2017-8558
vendor-advisory
-
securityfocus.com
/bid/99262
vdb-entry, third-party-advisory
-
securitytracker.com
/id/1038783
vdb-entry, third-party-advisory
-
securitytracker.com
/id/1038784
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2017-8558
- NVD CVE-2017-8558
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.