CVE-2017-0228

Name: CVE-2017-0228
Creator: NVD / NIST
Published: 2017-05-12T14:29:02.44+00:00
License: https://creativecommons.org/publicdomain/zero/1.0/

UnknownEPSS 16.99%

Last modified Jun 17, 2026

CVE-2017-0228 is a vulnerability of currently unknown severity. A remote code execution vulnerability exists in Microsoft browsers in the way JavaScript engines render when handling objects in memory, aka "Scripting Engine Memory Corruption Vulnerability." This CVE ID is unique from CVE-2017-0224, CVE-2017-0229, CVE-2017-0230, CVE-2017-0234, CVE-2017-0235, CVE-2017-0236, and CVE-2017-0238.. EPSS estimates a 16.99% chance of exploitation in the next 30 days.

Description

A remote code execution vulnerability exists in Microsoft browsers in the way JavaScript engines render when handling objects in memory, aka "Scripting Engine Memory Corruption Vulnerability." This CVE ID is unique from CVE-2017-0224, CVE-2017-0229, CVE-2017-0230, CVE-2017-0234, CVE-2017-0235, CVE-2017-0236, and CVE-2017-0238.

Metrics

EPSS Probability

16.99%

96.7th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

CWE-119

Affected Software

Vendor	Product	Versions
Microsoft	Edge	All versions
Microsoft	Internet Explorer	11

References

http://www.securityfocus.com/bid/98164Third Party Advisory, VDB Entry
http://www.securitytracker.com/id/1038425
http://www.securitytracker.com/id/1038426
https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2017-0228Patch, Vendor Advisory
http://www.securityfocus.com/bid/98164Third Party Advisory, VDB Entry
http://www.securitytracker.com/id/1038425
http://www.securitytracker.com/id/1038426
https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2017-0228Patch, Vendor Advisory

Timeline

Published: May 12, 2017
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2017-0228?

How severe is CVE-2017-0228?

Severity scoring for CVE-2017-0228 is pending analysis. The EPSS model estimates a 16.99% probability of exploitation in the next 30 days.

How do I fix CVE-2017-0228?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2017-0228?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST