How many CVEs have patched unregister_entry?

2 published CVEs changed unregister_entry in bytecodealliance/wasmtime, in 1 distinct patches totalling 280 changed lines, between 2024 and 2024.

What is the latest CVE that changed unregister_entry?

CVE-2024-47813 (Wasmtime race condition could lead to WebAssembly control-flow integrity and type safety violations), published 2024-10-09, changed lines 886 to 1012 of crates/wasmtime/src/runtime/type_registry.rs.

How does unregister_entry compare to the rest of bytecodealliance/wasmtime?

bytecodealliance/wasmtime has 27 CVEs with a located fix in total; 2 of them changed unregister_entry.

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
Bytecodealliance
Wasmtime
Unregister_entry

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
Bytecodealliance
Wasmtime
Unregister_entry

unregister_entry in bytecodealliance/wasmtime: Patched by 2 CVEs

bytecodealliance/wasmtime

Function

unregister_entry

Name: unregister_entry in bytecodealliance/wasmtime: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

crates/wasmtime/src/runtime/type_registry.rs

Last patched October 9, 2024

CVEs

That changed this function

Distinct patches

Backports counted once

280

Lines changed

Added plus removed

2024

Years

By CVE publication date

Overview

unregister_entry in bytecodealliance/wasmtime was changed by 2 published CVE fixes in 2024, in 1 distinct patches that added or removed 280 lines in total.

bytecodealliance/wasmtime has 27 CVEs with a located fix in total, so 7% of them touched this function.

CVEs that patched it

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

Wasmtime race condition could lead to WebAssembly control-flow integrity and type safety violations
CVE-2024-47813 · lines 886–1012 · +122 −18
Low · CVSS 1.0
EPSS 0.2%2024-10-09
Wasmtime runtime crash when combining tail calls with trapping imports
CVE-2024-47763 · lines 886–1012 · +122 −18
Medium · CVSS 6.8
EPSS 0.2%2024-10-09

Get an alert when the next CVE fix lands in bytecodealliance/wasmtime, with the patched functions.

Monitor wasmtime CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

1shared_type_index_to_slab_idcrates/wasmtime/src/runtime/type_registry.rs2 CVEs · 1 patches2024
2itercrates/wasmtime/src/runtime/type_registry.rs2 CVEs · 1 patches2024
3fieldcrates/wasmtime/src/runtime/type_registry.rs1 CVEs · 1 patches2024
4newcrates/wasmtime/src/runtime/type_registry.rs1 CVEs · 1 patches2024
5register_newcrates/wasmtime/src/runtime/type_registry.rs1 CVEs · 1 patches2024
6rootcrates/wasmtime/src/runtime/type_registry.rs1 CVEs · 1 patches2024
7as_occupied_mutcrates/wasmtime/src/runtime/type_registry.rs1 CVEs · 1 patches2024
8unwrapcrates/wasmtime/src/runtime/type_registry.rs1 CVEs · 1 patches2024

Other hotspots in the repository

Functions in bytecodealliance/wasmtime changed by the most CVE fixes.

and_then2 CVEs · crates/wasmtime/src/runtime/component/values.rs hostcall_fuel2 CVEs · crates/wasmtime/src/runtime/component/store.rs Done2 CVEs · crates/wasi-http/src/types_impl.rs Err2 CVEs · crates/wasi-http/src/body.rs Some2 CVEs · crates/wasi-http/src/body.rs as_ref2 CVEs · crates/wasi-http/src/types_impl.rs

All patched functions in bytecodealliance/wasmtime

Frequently asked questions

Common questions about CVE fixes to unregister_entry.

How many CVEs have patched unregister_entry?: 2 published CVEs changed unregister_entry in bytecodealliance/wasmtime, in 1 distinct patches totalling 280 changed lines, between 2024 and 2024.
What is the latest CVE that changed unregister_entry?: CVE-2024-47813 (Wasmtime race condition could lead to WebAssembly control-flow integrity and type safety violations), published 2024-10-09, changed lines 886 to 1012 of crates/wasmtime/src/runtime/type_registry.rs.
How does unregister_entry compare to the rest of bytecodealliance/wasmtime?: bytecodealliance/wasmtime has 27 CVEs with a located fix in total; 2 of them changed unregister_entry.
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

crates/wasmtime/src/runtime/type_registry.rs on GitHub (opens in a new tab)
All patched functions in bytecodealliance/wasmtime
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 bytecodealliance/wasmtime 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