CVE-2019-0829 json
ChakraCore Memory Corruption Vulnerability
published 7y ago modified 4mo ago also GHSA-5rq3-9wc9-m9c3 , EUVD-2022-2652
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 9.0%
- EPSS 9.0% chance of exploitation in 30 days, percentile 95%
- public exploits
- 0
- none known
Summary
A remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0806, CVE-2019-0810, CVE-2019-0812, CVE-2019-0860, CVE-2019-0861.
Patch / fix
- nuget Microsoft.ChakraCore 1.11.8
- microsoft chakracore 1.11.8
Is CVE-2019-0829 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 FencerExploit prediction
8.96% 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.8 |
1.11.8 |
Affected products
- Microsoft Microsoft Edge
- Microsoft ChakraCore
Classification
- Weakness
-
- CWE-787 Out-of-bounds Write
References
-
portal.msrc.microsoft.com
/en-US/security-guidance/advisory/CVE-2019-0829
web, patch, vendor-advisory
-
github.com
/chakra-core/ChakraCore/pull/6087
web
-
github.com
/chakra-core/ChakraCore/commit/b03a96112fb05158a040caba88919cd70648f09f
web
-
nvd.nist.gov
/vuln/detail/CVE-2019-0829
advisory
-
github.com
/chakra-core/ChakraCore
package
Sources
- CVE List CVE-2019-0829
- GitHub Advisory GHSA-5rq3-9wc9-m9c3
- NVD CVE-2019-0829
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.