How many CVEs have patched TryReleaseNonHiPriWorkItem?

3 published CVEs changed TryReleaseNonHiPriWorkItem in chakra-core/ChakraCore, in 1 distinct patches totalling 33 changed lines, between 2017 and 2017.

What is the latest CVE that changed TryReleaseNonHiPriWorkItem?

CVE-2017-11862 (Chakra Core vulnerable to privilege escalation due to type confusion), published 2017-11-15, changed lines 3194 to 3205 of lib/Backend/NativeCodeGenerator.cpp.

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

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

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

Security data

Weaknesses (CWE)The MITRE CWE weakness catalog
Attack Patterns (CAPEC)MITRE CAPEC attack patterns
CNAsNumbering authorities and report cards
VendorsVulnerabilities by vendor
Patched FunctionsWhere CVE fixes land in code

Tools

CVSS CalculatorScore CVSS 4.0, 3.1, 3.0 & 2.0
Badge BuilderEmbeddable SVG badges for READMEs

Resources

LearnSecurity guides
Data SourcesCVE data sources

About Blog Pricing Demo

Home
Patched Functions
Chakra Core
Chakracore
TryReleaseNonHiPriWorkItem

RadicalNotion.AI

We do not sell or share your personal information.

Security Data

CWE Directory
CAPEC Directory
CNA Directory
CNA Leaderboard
CNA Report Cards
Vendor Directory
Patched Functions
Data Sources

Calculators

CVSS Calculator
CVSS 4.0
CVSS 3.1
CVSS 3.0
CVSS 2.0
Badge Builder

Platform

My Vulnerabilities
Insights
Notifications
Pricing

Learn

Guides
What is a CVE?
What is CVSS?
The CISA KEV catalog
What is EPSS?

Company

About
Blog
Careers
Contact
Demo

Account

Legal

Security
Privacy
Terms

RadicalNotion.AI

Security data

Weaknesses (CWE)The MITRE CWE weakness catalog
Attack Patterns (CAPEC)MITRE CAPEC attack patterns
CNAsNumbering authorities and report cards
VendorsVulnerabilities by vendor
Patched FunctionsWhere CVE fixes land in code

Tools

CVSS CalculatorScore CVSS 4.0, 3.1, 3.0 & 2.0
Badge BuilderEmbeddable SVG badges for READMEs

Resources

LearnSecurity guides
Data SourcesCVE data sources

About Blog Pricing Demo

Home
Patched Functions
Chakra Core
Chakracore
TryReleaseNonHiPriWorkItem

TryReleaseNonHiPriWorkItem in chakra-core/ChakraCore: Patched by 3 CVEs

chakra-core/ChakraCore

Function

TryReleaseNonHiPriWorkItem

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

lib/Backend/NativeCodeGenerator.cpp

Last patched November 15, 2017

CVEs

That changed this function

Distinct patches

Backports counted once

Lines changed

Added plus removed

2017

Years

By CVE publication date

Overview

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

Chakra Core vulnerable to privilege escalation due to type confusion
CVE-2017-11862 · lines 3194–3205 · +2 −9
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 3194–3205 · +2 −9
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 3194–3205 · +2 −9
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.

1FromVarlib/Backend/NativeCodeGenerator.cpp3 CVEs · 2 patches2017

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

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

lib/Backend/NativeCodeGenerator.cpp on GitHub (opens in a new tab)
All patched functions in chakra-core/ChakraCore
Patched functions directory

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

On this page

Overview
CVEs that patched it
Other functions in these files
Other hotspots in the repository
FAQ
References