Repository navigation
deps: wasmtime 36.0.21 and two reviewed audit exceptions - #602
Merged
Merged
Conversation
Built-by: Codex
Contributor
Author
|
Main: Merged on Anders's explicit authorization in chat (19 Nov). All nine required checks were green on the pull request's head. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Deepen notes
f6d819571;elastos/crates/elastos-compute/Cargo.toml:16(wasmtime features,threadson);elastos/crates/elastos-compute/src/providers/component.rs:80(the engine sets the component model and fuel only); CI's audit loop at.github/workflows/ci.yml:128; both upstream advisory pages, read directly.cargo update -p wasmtime --precise 36.0.21per lock file, parsed lock comparison, source searches with a known positive for each, CI's audit loop over all 34 lock files, a full Linux check of the committed head and a second Linux run with--locked.Change
Eight wasmtime advisories entered the RustSec database on 19 Nov at 08:42 UTC. Five flag wasmtime 36.0.20 in
elastos/Cargo.lockandcapsules/object-provider/Cargo.lock, which turns the audit red and cancels every pull request's CI.elastos/Cargo.lockand 12 across 11 in the object-provider lock (mostlywindows-sys, plus syn fordata-encoding-macro-internaland getrandom fortempfile), all inside their declared ranges and all to versions already in the lock.elastos/.cargo/audit.toml: RUSTSEC-2026-0567 and -0573. The RustSec entries list no fix and no unaffected range for the 36 line. The upstream advisories list affected versions from 39.0.0 and from 47.0.0, so 36 is not affected. Each entry gives the upstream range, the link, the fact about our build, and when to remove it.wasmtime-wasiorwasmtime-wasi-httpin the locks, noget_module_exportcall, thethreadsfeature is on, and no heap movement or reservation setting is changed.Not verified: the advisories' exploit reproductions, macOS and Windows builds, installed-product acceptance. Compilation ran on Linux.
Follow-ups, not in this change: ask RustSec to record the unaffected ranges so the two exceptions can go; the shared full Linux runner builds without
--locked.