How many CVEs have patched ParseFncNames?

3 published CVEs changed ParseFncNames in chakra-core/ChakraCore, in 2 distinct patches totalling 23 changed lines, between 2016 and 2018.

What is the latest CVE that changed ParseFncNames?

CVE-2018-0936 (ChakraCore RCE Vulnerability), published 2018-03-14, changed lines 6564 of lib/Parser/Parse.cpp.

How does ParseFncNames compare to the rest of chakra-core/ChakraCore?

chakra-core/ChakraCore has 205 CVEs with a located fix in total; 3 of them changed ParseFncNames.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

chakra-core/ChakraCore

Function

ParseFncNames

Name: ParseFncNames in chakra-core/ChakraCore: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

lib/Parser/Parse.cpp

Last patched March 14, 2018

3

CVEs

That changed this function

2

Distinct patches

Backports counted once

23

Lines changed

Added plus removed

2016–2018

Years

By CVE publication date

Overview

ParseFncNames in chakra-core/ChakraCore was changed by 3 published CVE fixes between 2016 and 2018, in 2 distinct patches that added or removed 23 lines in total.

chakra-core/ChakraCore has 205 CVEs with a located fix in total, so 1% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed ParseFncNames, newest first, with the lines each fix touched.

ChakraCore RCE Vulnerability
CVE-2018-0936 · line 6564 · +0 −9
High · CVSS 7.5
EPSS 15.4%2018-03-14
ChakraCore RCE Vulnerability
CVE-2016-3350 · line 5906 · +0 −7
High · CVSS 7.5
EPSS 15.3%2016-09-14
ChakraCore RCE Vulnerability
CVE-2016-3377 · line 5906 · +0 −7
High · CVSS 7.5
EPSS 15.9%2016-09-14

Get an alert when the next CVE fix lands in chakra-core/ChakraCore, with the patched functions.

Monitor ChakraCore CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in chakra-core/ChakraCore changed by the most CVE fixes.

Optimize29 CVEs · lib/Backend/GlobOptArrays.cpp StartEmitFunction17 CVEs · lib/Runtime/ByteCode/ByteCodeEmitter.cpp StartEmitCatch15 CVEs · lib/Runtime/ByteCode/ByteCodeEmitter.cpp InsertValueCompensation14 CVEs · lib/Backend/GlobOpt.cpp TryLowerNewScObjectWithFixedCtorCache14 CVEs · lib/Backend/Lower.cpp EndVisitBlock14 CVEs · lib/Runtime/ByteCode/ByteCodeGenerator.cpp

All patched functions in chakra-core/ChakraCore

Frequently asked questions

Common questions about CVE fixes to ParseFncNames.

How many CVEs have patched ParseFncNames?: 3 published CVEs changed ParseFncNames in chakra-core/ChakraCore, in 2 distinct patches totalling 23 changed lines, between 2016 and 2018.
What is the latest CVE that changed ParseFncNames?: CVE-2018-0936 (ChakraCore RCE Vulnerability), published 2018-03-14, changed lines 6564 of lib/Parser/Parse.cpp.
How does ParseFncNames compare to the rest of chakra-core/ChakraCore?: chakra-core/ChakraCore has 205 CVEs with a located fix in total; 3 of them changed ParseFncNames.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track chakra-core/ChakraCore CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing