Skip to content
Cyber Threat
CTI Academy Sponsor CTI Academy
HIGH · CVSS 7.5 CISA Known Exploited Vulnerability

CVE-2019-0752

Microsoft Internet Explorer Type Confusion Vulnerability

Microsoft Internet Explorer

A remote code execution vulnerability exists in the way that the scripting engine handles objects in memory in Internet Explorer, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0739, CVE-2019-0753, CVE-2019-0862.

CVSS
7.5
HIGH
EPSS
81.7%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
9 Apr 2019
CWE-843

Exploitation status

CISA Known Exploited Vulnerabilities

Listed by CISA on 15 February 2022. US federal agencies were required to remediate it by 15 August 2022. CISA records this vulnerability as known to be used in ransomware campaigns.

EPSS — exploitation probability

FIRST puts the probability of exploitation activity in the next 30 days at 81.7%, which is higher than 99.6% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

Frequently asked questions

Is CVE-2019-0752 being exploited by ransomware groups?

No ransomware group in this database is currently recorded as exploiting CVE-2019-0752.

What does CVE-2019-0752 affect?

CVE-2019-0752 affects Microsoft Internet Explorer. A remote code execution vulnerability exists in the way that the scripting engine handles objects in memory in Internet Explorer, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0739, CVE-2019-0753, CVE-2019-0862.

How severe is CVE-2019-0752?

CVE-2019-0752 is rated HIGH with a CVSS base score of 7.5. EPSS puts the probability of exploitation in the next 30 days at 81.7%, higher than 99.6% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 15 August 2022.

How should organisations respond to CVE-2019-0752?

Apply the vendor patch for Microsoft Internet Explorer as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.