Debian Package Tracker
Register | Log in
Subscribe

rust-wasmtime

low-level retargetable code generator - Rust source code

Choose email to subscribe with

general
  • source: rust-wasmtime (main)
  • version: 26.0.1+dfsg-3
  • maintainer: Jonas Smedegaard (DMD) (LowNMU)
  • arch: all
  • std-ver: 4.7.0
  • VCS: Git (Browse, QA)
versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]
[pool directory]
  • testing: 26.0.1+dfsg-3
  • unstable: 26.0.1+dfsg-3
versioned links
  • 26.0.1+dfsg-3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
binaries
  • librust-cranelift-dev
action needed
Multiarch hinter reports 1 issue(s) high
There are issues with the multiarch metadata for this package.
  • librust-cranelift-dev should be Architecture: any + Multi-Arch: same
Created: 2023-08-21 Last update: 2025-07-27 10:03
A new upstream version is available: 35.0.0 high
A new upstream version 35.0.0 is available, you should consider packaging it.
Created: 2024-01-29 Last update: 2025-07-27 04:31
1 security issue in trixie high

There is 1 open security issue in trixie.

1 important issue:
  • CVE-2025-53901: Wasmtime is a runtime for WebAssembly. Prior to versions 24.0.4, 33.0.2, and 34.0.2, a bug in Wasmtime's implementation of the WASIp1 set of import functions can lead to a WebAssembly guest inducing a panic in the host (embedder). The specific bug is triggered by calling `path_open` after calling `fd_renumber` with either two equal argument values or a second argument being equal to a previously-closed file descriptor number value. The corrupt state introduced in `fd_renumber` will lead to the subsequent opening of a file descriptor to panic. This panic cannot introduce memory unsafety or allow WebAssembly to break outside of its sandbox, however. There is no possible heap corruption or memory unsafety from this panic. This bug is in the implementation of Wasmtime's `wasmtime-wasi` crate which provides an implementation of WASIp1. The bug requires a specially crafted call to `fd_renumber` in addition to the ability to open a subsequent file descriptor. Opening a second file descriptor is only possible when a preopened directory was provided to the guest, and this is common amongst embeddings. A panic in the host is considered a denial-of-service vector for WebAssembly embedders and is thus a security issue in Wasmtime. This bug does not affect WASIp2 and embedders using components. In accordance with Wasmtime's release process, patch releases are available as 24.0.4, 33.0.2, and 34.0.2. Users of other release of Wasmtime are recommended to move to a supported release of Wasmtime. Embedders who are using components or are not providing guest access to create more file descriptors (e.g. via a preopened filesystem directory) are not affected by this issue. Otherwise, there is no workaround at this time, and affected embeddings are recommended to update to a patched version which will not cause a panic in the host.
Created: 2025-07-19 Last update: 2025-07-19 23:58
1 security issue in sid high

There is 1 open security issue in sid.

1 important issue:
  • CVE-2025-53901: Wasmtime is a runtime for WebAssembly. Prior to versions 24.0.4, 33.0.2, and 34.0.2, a bug in Wasmtime's implementation of the WASIp1 set of import functions can lead to a WebAssembly guest inducing a panic in the host (embedder). The specific bug is triggered by calling `path_open` after calling `fd_renumber` with either two equal argument values or a second argument being equal to a previously-closed file descriptor number value. The corrupt state introduced in `fd_renumber` will lead to the subsequent opening of a file descriptor to panic. This panic cannot introduce memory unsafety or allow WebAssembly to break outside of its sandbox, however. There is no possible heap corruption or memory unsafety from this panic. This bug is in the implementation of Wasmtime's `wasmtime-wasi` crate which provides an implementation of WASIp1. The bug requires a specially crafted call to `fd_renumber` in addition to the ability to open a subsequent file descriptor. Opening a second file descriptor is only possible when a preopened directory was provided to the guest, and this is common amongst embeddings. A panic in the host is considered a denial-of-service vector for WebAssembly embedders and is thus a security issue in Wasmtime. This bug does not affect WASIp2 and embedders using components. In accordance with Wasmtime's release process, patch releases are available as 24.0.4, 33.0.2, and 34.0.2. Users of other release of Wasmtime are recommended to move to a supported release of Wasmtime. Embedders who are using components or are not providing guest access to create more file descriptors (e.g. via a preopened filesystem directory) are not affected by this issue. Otherwise, there is no workaround at this time, and affected embeddings are recommended to update to a patched version which will not cause a panic in the host.
Created: 2025-07-19 Last update: 2025-07-19 23:58
lintian reports 1 error high
Lintian reports 1 error about this package. You should make the package lintian clean getting rid of them.
Created: 2025-02-18 Last update: 2025-02-18 21:03
Fails to build during reproducibility testing normal
A package building reproducibly enables third parties to verify that the source matches the distributed binaries. It has been identified that this source package produced different results, failed to build or had other issues in a test environment. Please read about how to improve the situation!
Created: 2025-03-09 Last update: 2025-07-27 10:03
ITP: Someone is planning to reintroduce this package. normal
The WNPP database contains an ITP (Intent To Package) entry for this package. This is probably an error, as it has already been packaged. Please see bug number #1041463 for more information.
Created: 2023-08-02 Last update: 2023-08-02 03:27
Standards version of the package is outdated. wishlist
The package should be updated to follow the last version of Debian Policy (Standards-Version 4.7.2 instead of 4.7.0).
Created: 2025-02-21 Last update: 2025-02-27 13:25
news
[rss feed]
  • [2025-02-23] rust-wasmtime 26.0.1+dfsg-3 MIGRATED to testing (Debian testing watch)
  • [2025-02-18] Accepted rust-wasmtime 26.0.1+dfsg-3 (source) into unstable (Jonas Smedegaard)
  • [2025-02-17] rust-wasmtime 26.0.1+dfsg-2 MIGRATED to testing (Debian testing watch)
  • [2025-02-11] Accepted rust-wasmtime 26.0.1+dfsg-2 (source) into unstable (Jonas Smedegaard)
  • [2025-02-09] Accepted rust-wasmtime 26.0.1+dfsg-1 (source) into unstable (Jonas Smedegaard)
  • [2025-02-09] Accepted rust-wasmtime 23.0.3+dfsg-1 (source) into unstable (Jonas Smedegaard)
  • [2025-02-09] Accepted rust-wasmtime 21.0.2+dfsg-3 (source) into unstable (Jonas Smedegaard)
  • [2025-02-09] Accepted rust-wasmtime 21.0.2+dfsg-2 (source) into unstable (Jonas Smedegaard)
  • [2025-01-08] rust-wasmtime 21.0.2+dfsg-1.1 MIGRATED to testing (Debian testing watch)
  • [2025-01-02] Accepted rust-wasmtime 21.0.2+dfsg-1.1 (source) into unstable (Peter Michael Green)
  • [2024-11-22] rust-wasmtime 21.0.2+dfsg-1 MIGRATED to testing (Debian testing watch)
  • [2024-11-16] Accepted rust-wasmtime 21.0.2+dfsg-1 (source) into unstable (Jonas Smedegaard)
  • [2024-11-10] rust-wasmtime 19.0.0+dfsg-4 MIGRATED to testing (Debian testing watch)
  • [2024-11-04] Accepted rust-wasmtime 19.0.0+dfsg-4 (source) into unstable (Jonas Smedegaard)
  • [2024-09-09] rust-wasmtime REMOVED from testing (Debian testing watch)
  • [2024-07-18] rust-wasmtime 19.0.0+dfsg-3 MIGRATED to testing (Debian testing watch)
  • [2024-07-12] Accepted rust-wasmtime 19.0.0+dfsg-3 (source) into unstable (Jonas Smedegaard)
  • [2024-05-27] rust-wasmtime 19.0.0+dfsg-2 MIGRATED to testing (Debian testing watch)
  • [2024-05-17] Accepted rust-wasmtime 19.0.0+dfsg-2 (source) into unstable (Jonas Smedegaard)
  • [2024-05-17] Accepted rust-wasmtime 19.0.0+dfsg-1 (source) into unstable (Jonas Smedegaard)
  • [2024-02-22] Accepted rust-wasmtime 18.0.1+dfsg-1 (source) into experimental (Jonas Smedegaard)
  • [2024-02-22] rust-wasmtime 16.0.0+dfsg-3 MIGRATED to testing (Debian testing watch)
  • [2024-02-17] Accepted rust-wasmtime 16.0.0+dfsg-3 (source) into unstable (Jonas Smedegaard)
  • [2024-01-07] rust-wasmtime 16.0.0+dfsg-2 MIGRATED to testing (Debian testing watch)
  • [2024-01-01] Accepted rust-wasmtime 16.0.0+dfsg-2 (source) into unstable (Jonas Smedegaard)
  • [2023-12-30] Accepted rust-wasmtime 16.0.0+dfsg-1 (source) into experimental (Jonas Smedegaard)
  • [2023-12-30] Accepted rust-wasmtime 15.0.1+dfsg-4 (source) into unstable (Jonas Smedegaard)
  • [2023-12-30] Accepted rust-wasmtime 15.0.1+dfsg-3 (source) into unstable (Jonas Smedegaard)
  • [2023-12-30] Accepted rust-wasmtime 15.0.1+dfsg-2 (source) into experimental (Jonas Smedegaard)
  • [2023-12-30] Accepted rust-wasmtime 15.0.1+dfsg-1 (source) into experimental (Jonas Smedegaard)
  • 1
  • 2
bugs [bug history graph]
  • all: 3
  • RC: 0
  • I&N: 1
  • M&W: 2
  • F&P: 0
  • patch: 0
links
  • homepage
  • lintian (1, 0)
  • buildd: logs, reproducibility
  • popcon
  • browse source code
  • edit tags
  • other distros
  • security tracker
  • debian patches
  • debci
ubuntu Ubuntu logo [Information about Ubuntu for Debian Developers]
  • version: 26.0.1+dfsg-3

Debian Package Tracker — Copyright 2013-2025 The Distro Tracker Developers
Report problems to the tracker.debian.org pseudo-package in the Debian BTS.
Documentation — Bugs — Git Repository — Contributing