How many CVEs have patched strategy?

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

What is the latest CVE that changed strategy?

CVE-2024-47763 (Wasmtime runtime crash when combining tail calls with trapping imports), published 2024-10-09, changed lines 1027 of crates/wasmtime/src/config.rs.

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

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

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

bytecodealliance/wasmtime

Function

strategy

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

crates/wasmtime/src/config.rs

Last patched October 9, 2024

1

CVEs

That changed this function

1

Distinct patches

Backports counted once

2

Lines changed

Added plus removed

2024

Years

By CVE publication date

Overview

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

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

CVEs that patched it

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

Wasmtime runtime crash when combining tail calls with trapping imports
CVE-2024-47763 · line 1027 · +1 −1
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.

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

How many CVEs have patched strategy?: 1 published CVEs changed strategy in bytecodealliance/wasmtime, in 1 distinct patches totalling 2 changed lines, between 2024 and 2024.
What is the latest CVE that changed strategy?: CVE-2024-47763 (Wasmtime runtime crash when combining tail calls with trapping imports), published 2024-10-09, changed lines 1027 of crates/wasmtime/src/config.rs.
How does strategy compare to the rest of bytecodealliance/wasmtime?: bytecodealliance/wasmtime has 27 CVEs with a located fix in total; 1 of them changed strategy.
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 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