CVE-2019-0639 — Vulnerability in Microsoft.ChakraCore — CVE Details
High severity vulnerability that affects Microsoft.ChakraCore
Summary
Advisory Timeline
- First published April 9, 2019 (2743 days ago).
- Last revised February 16, 2024 — 1774 days after initial publication.
Remediation
Upgrade to the fixed version using your package manager.
dotnet add package Microsoft.ChakraCore --version 1.11.7
After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.
Affected Packages (1)
Affects 1 ecosystem: nuget (1).
| Package | Ecosystem | Affected | Fixed In |
|---|---|---|---|
| Microsoft.ChakraCore | nuget | 1.10.0, 1.10.1, 1.10.2, 1.11.0 (+39 more) | 1.11.7 |
Vulnerability Classification
Common Weakness Enumeration (CWE) identifiers for this vulnerability type.
- CWE-190Integer OverflowMITRE
CVSS Score Breakdown
What the CVSS (Common Vulnerability Scoring System) 7.5 score means for each attack dimension.
CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
References
Frequently Asked Questions
- What is CVE-2019-0639?
- High severity vulnerability that affects Microsoft.ChakraCore This vulnerability has been assigned a severity rating of HIGH (CVSS score: 7.5/10).
- How do I check if my project is affected by CVE-2019-0639?
- CVE-2019-0639 affects Microsoft.ChakraCore. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2019-0639 and 200,000+ other known vulnerabilities.
Severity & Exploitability
High exploitability or significant impact. Prioritize remediation within days.
Also Known As
Related CVEs
- CVE-2017-0252CRITICAL
ChakraCore RCE Vulnerability
- CVE-2018-8266HIGH
ChakraCore RCE Vulnerability
- CVE-2020-0711HIGH
ChakraCore RCE Vulnerability
- CVE-2016-3382HIGH
ChakraCore RCE Vulnerability
- CVE-2019-0989HIGH
Chakra Scripting Engine Memory Corruption Vulnerability
- CVE-2019-0609HIGH
High severity vulnerability that affects Microsoft.ChakraCore
- CVE-2019-1195HIGH
Out-of-bounds write in Microsoft.ChakraCore
- CVE-2016-3377HIGH
ChakraCore RCE Vulnerability
Check if you're affected
Scan your dependencies to see if this vulnerability affects your projects.
Scan Your Dependencies