dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 15 Aug 2022. Known ransomware use
Internet ExplorerApplication · Microsoft

CVE-2019-0752

HIGH · 7.5 CVSS v3.1 Published 2019-04-09
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
In the wild Ransomware High EPSS Public exploit Remotely reachable No privileges Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

CVE-2019-0752 is a memory corruption vulnerability in Internet Explorer's scripting engine that allows remote code execution via specially crafted web pages. The vulnerability stems from improper handling of objects in memory by the scripting engine, enabling an attacker to execute arbitrary code when a user visits a malicious website.

MitigationApply the Microsoft security update for CVE-2019-0752 via Windows Update or WSUS, and consider using Microsoft Edge or alternative browsers as Internet Explorer reaches end-of-life.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Internet ExplorerApplication
Affected:= 11= 10

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Internet Explorer version
    Open Command Prompt and run: reg query "HKLM\SOFTWARE\Microsoft\Internet Explorer" /v Version
    Affected if The returned version shows 10.x or 11.x (e.g., 11.0.9600.XXXXX)
  2. Confirm JScript scripting engine version
    Check the JScript DLL version by running: reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages" /s | findstr -i "JScript"
    Affected if The package version corresponds to an unpatched JScript.dll for IE 10 or 11
  3. Check for active Internet Explorer processes
    Open Task Manager or run: tasklist | findstr -i iexplore
    Affected if Any iexplore.exe processes are running on the system
  4. Verify Enhanced Protected Mode status
    Open Internet Explorer, go to Internet Options > Security tab, check 'Enable Enhanced Protected Mode' for each zone
    Affected if Enhanced Protected Mode is disabled for Internet or Intranet zones (vulnerability has higher impact)

The system is affected if Internet Explorer version 10 or 11 is installed and the associated security updates for CVE-2019-0752 have not been applied, regardless of whether EPM is enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch portal.msrc.microsoft.com →
Interim mitigation

Apply the Microsoft security update for CVE-2019-0752 via Windows Update or WSUS, and consider using Microsoft Edge or alternative browsers as Internet Explorer reaches end-of-life.

Recommended fix Moderate confidence
  1. Apply the cumulative security update for Internet Explorer. For CVE-2019-0752, this was addressed in the Windows security updates released April 2019.
  2. On Windows 10: Install Windows Update KB4493472 or later cumulative update.
  3. On Windows Server 2016/2019: Install the corresponding Windows Server security update.
  4. On Windows 7/8.1: Install the associated Internet Explorer cumulative security update from April 2019.
  5. Verify the update is installed by checking Windows Update history and confirming the KB number matches the April 2019 security release.
Caveat Applying security updates may require system restart; ensure proper change management and backup procedures are followed

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Internet Explorer Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,540
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-0752 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-0752 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data