CVE-2017-0201

Name: CVE-2017-0201
Creator: NVD / NIST
Published: 2017-04-12T14:59:01.203+00:00
License: https://creativecommons.org/publicdomain/zero/1.0/

UnknownEPSS 13.88%

Last modified Jun 17, 2026

CVE-2017-0201 is a vulnerability of currently unknown severity. A remote code execution vulnerability exists in Internet Explorer in the way that the JScript and VBScript engines render when handling objects in memory. The vulnerability could corrupt memory in such a way that an attacker could execute arbitrary code in the context of the current user, aka "Scripting Engine Memory Corruption Vulnerability." This CVE ID is unique from CVE-2017-0093.. EPSS estimates a 13.88% chance of exploitation in the next 30 days.

Description

A remote code execution vulnerability exists in Internet Explorer in the way that the JScript and VBScript engines render when handling objects in memory. The vulnerability could corrupt memory in such a way that an attacker could execute arbitrary code in the context of the current user, aka "Scripting Engine Memory Corruption Vulnerability." This CVE ID is unique from CVE-2017-0093.

Metrics

EPSS Probability

13.88%

96.0th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

CWE-119

Affected Software

Vendor	Product	Versions
Microsoft	Internet Explorer	9
Microsoft	Internet Explorer	10

References

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

Timeline

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

Frequently Asked Questions

What is CVE-2017-0201?

How severe is CVE-2017-0201?

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

How do I fix CVE-2017-0201?

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-0201?

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

Scan your code now

Source: NVD / NIST