Vulnerability in wasmtime (CVE-2024-30266)

Summary

Vulnerability in wasmtime (CVE-2024-30266). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 19.0.1 or later.

Original description

The description as published by the source.

This is an entry in the RustSec database for the Wasmtime security advisory
located at
https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-75hq-h6g9-h4q5.
For more information see the GitHub-hosted security advisory.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2024-30266 has been found in wasmtime.
Risk of unauthorized operations or information disclosure.
What to do: upgrade wasmtime to 19.0.1 or later.
If unsure, ask your IT team or search "wasmtime CVE-2024-30266" on the vendor's site.

CVE-2024-30266 (wasmtime)
Attack vector: local / no user interaction
Patched: 19.0.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in wasmtime.

📍 Affected scope

Check the vendor advisory for the affected versions of wasmtime.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 19.0.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'wasmtime' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'wasmtime' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で wasmtime を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade wasmtime to 19.0.1
```
ステージング環境で 19.0.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

crates.io wasmtime

[{"type":"SEMVER","events":[{"introduced":"19.0.0"},{"fixed":"19.0.1"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

Debian DEBIAN-CVE-2024-30266 rust-wasmtime Fixed in: 21.0.2+dfsg-1

References

advisory rustsec.org
advisory github.com
package crates.io
report github.com