How many CVEs have patched ParseFncDecl?

3 published CVEs changed ParseFncDecl in chakra-core/ChakraCore, in 2 distinct patches totalling 12 changed lines, between 2017 and 2017.

What is the latest CVE that changed ParseFncDecl?

CVE-2017-11862 (Chakra Core vulnerable to privilege escalation due to type confusion), published 2017-11-15, changed lines 5201 to 5204 of lib/Parser/Parse.cpp.

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

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

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

ParseFncDecl

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

lib/Parser/Parse.cpp

Last patched November 15, 2017

3

CVEs

That changed this function

2

Distinct patches

Backports counted once

12

Lines changed

Added plus removed

2017

Years

By CVE publication date

Overview

ParseFncDecl in chakra-core/ChakraCore was changed by 3 published CVE fixes in 2017, in 2 distinct patches that added or removed 12 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 ParseFncDecl, newest first, with the lines each fix touched.

Chakra Core vulnerable to privilege escalation due to type confusion
CVE-2017-11862 · lines 5201–5204 · +4 −0
High · CVSS 7.5
EPSS 7.9%2017-11-15
Chakra Core vulnerable to privilege escalation when writing to JavaScript null scope objects
CVE-2017-11870 · lines 5197–5200 · +4 −0
High · CVSS 7.5
EPSS 59.6%2017-11-15
Chakra Core vulnerable to privilege escalation due to reading an invalid pointer
CVE-2017-11871 · lines 5201–5204 · +4 −0
High · CVSS 7.5
EPSS 8.0%2017-11-15

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 ParseFncDecl.

How many CVEs have patched ParseFncDecl?: 3 published CVEs changed ParseFncDecl in chakra-core/ChakraCore, in 2 distinct patches totalling 12 changed lines, between 2017 and 2017.
What is the latest CVE that changed ParseFncDecl?: CVE-2017-11862 (Chakra Core vulnerable to privilege escalation due to type confusion), published 2017-11-15, changed lines 5201 to 5204 of lib/Parser/Parse.cpp.
How does ParseFncDecl compare to the rest of chakra-core/ChakraCore?: chakra-core/ChakraCore has 205 CVEs with a located fix in total; 3 of them changed ParseFncDecl.
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