How many CVEs have patched MayHaveImplicitCall?

5 published CVEs changed MayHaveImplicitCall in chakra-core/ChakraCore, in 1 distinct patches totalling 15 changed lines, between 2019 and 2019.

What is the latest CVE that changed MayHaveImplicitCall?

CVE-2019-1107 (Out-of-bounds write), published 2019-07-29, changed lines 1141 to 1142 of lib/Backend/Opnd.h.

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

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

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

MayHaveImplicitCall

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

lib/Backend/Opnd.h

Last patched July 29, 2019

5

CVEs

That changed this function

1

Distinct patches

Backports counted once

15

Lines changed

Added plus removed

2019

Years

By CVE publication date

Overview

MayHaveImplicitCall in chakra-core/ChakraCore was changed by 5 published CVE fixes in 2019, in 1 distinct patches that added or removed 15 lines in total.

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

CVEs that patched it

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

Out-of-bounds write
CVE-2019-1107 · lines 1141–1142 · +2 −1
High · CVSS 7.5
EPSS 9.3%2019-07-29
Out-of-bounds write
CVE-2019-1106 · lines 1141–1142 · +2 −1
High · CVSS 7.5
EPSS 9.2%2019-07-29
Out-of-bounds write
CVE-2019-1103 · lines 1141–1142 · +2 −1
High · CVSS 7.5
EPSS 9.2%2019-07-29
Out-of-bounds write
CVE-2019-1092 · lines 1141–1142 · +2 −1
High · CVSS 7.5
EPSS 8.9%2019-07-15
Out-of-bounds write
CVE-2019-1062 · lines 1141–1142 · +2 −1
High · CVSS 7.5
EPSS 8.9%2019-07-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 MayHaveImplicitCall.

How many CVEs have patched MayHaveImplicitCall?: 5 published CVEs changed MayHaveImplicitCall in chakra-core/ChakraCore, in 1 distinct patches totalling 15 changed lines, between 2019 and 2019.
What is the latest CVE that changed MayHaveImplicitCall?: CVE-2019-1107 (Out-of-bounds write), published 2019-07-29, changed lines 1141 to 1142 of lib/Backend/Opnd.h.
How does MayHaveImplicitCall compare to the rest of chakra-core/ChakraCore?: chakra-core/ChakraCore has 205 CVEs with a located fix in total; 5 of them changed MayHaveImplicitCall.
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