Skip to content
Fencer Intel
high 7.5

CVE-2019-0911 json

Out-of-bounds write

published 7y ago modified 4mo ago also GHSA-9735-p6r2-2hgh , EUVD-2021-0638

cvss
7.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
9.1%
EPSS 9.1% chance of exploitation in 30 days, percentile 95%
public exploits
0
none known

Summary

A remote code execution vulnerability exists in the way the scripting engine handles objects in memory in Microsoft browsers, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0884, CVE-2019-0918.

Patch / fix

  • nuget Microsoft.ChakraCore 1.11.9
  • microsoft chakracore 1.11.9

Is CVE-2019-0911 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

9.09% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 7.5 CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 7.6 AV:N/AC:H/Au:N/C:C/I:C/A:C
GitHub 3.0 7.5 CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
nuget Microsoft.ChakraCore
<1.11.9
1.11.9

Affected products

  • Microsoft Internet Explorer 11
  • Microsoft Internet Explorer 11 on Windows Server 2012
  • Microsoft Internet Explorer 11 on Windows 10 Version 1903 for 32-bit Systems
  • Microsoft Internet Explorer 11 on Windows 10 Version 1903 for x64-based Systems
  • Microsoft Internet Explorer 11 on Windows 10 Version 1903 for ARM64-based Systems
  • Microsoft Internet Explorer 10
  • Microsoft Microsoft Edge
  • Microsoft Microsoft Edge on Windows 10 Version 1903 for 32-bit Systems
  • Microsoft Microsoft Edge on Windows 10 Version 1903 for x64-based Systems
  • Microsoft Microsoft Edge on Windows 10 Version 1903 for ARM64-based Systems
  • Microsoft ChakraCore

Classification

Weakness

References

Sources

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.