← Back
GHSA-fhvh-vw7h-9xf3
Vulnerability in libcrux-ml-dsa (GHSA-fhvh-vw7h-9xf3)
Summary
vulnerability in libcrux-ml-dsa (GHSA-fhvh-vw7h-9xf3). Risk of unauthorized operations or information disclosure. Exploitable via ``use_hint``. Mitigation: upgrade to `0.0.9` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-fhvh-vw7h-9xf3** has been found in libcrux-ml-dsa.
Attackers can target a specific entry point like ``use_hint`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade libcrux-ml-dsa to **0.0.9** or later.
If unsure, ask your IT team or search "libcrux-ml-dsa GHSA-fhvh-vw7h-9xf3" on the vendor's site.
GHSA-fhvh-vw7h-9xf3 (libcrux-ml-dsa) — CWE-347 /
Attack surface: `use_hint`
Patched: `0.0.9` — 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** (CWE-347) exists in libcrux-ml-dsa. Attackers reach the vulnerable code path via ``use_hint`` without authentication.
📍 Affected scope
libcrux-ml-dsa — . Attack surface: `use_hint`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.0.9**.
🛡️ 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 'libcrux-ml-dsa' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'libcrux-ml-dsa' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `libcrux-ml-dsa` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade libcrux-ml-dsa to 0.0.9ステージング環境で 0.0.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
rust
libcrux-ml-dsa
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.0.9"}]}]
crates.io
libcrux-ml-dsa
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.0.9"}]}]
References
- package https://github.com/cryspen/libcrux
- package https://crates.io/crates/libcrux-ml-dsa
- web https://github.com/C2SP/wycheproof/pull/234
- web https://github.com/cryspen/libcrux/pull/1398
- web https://github.com/tink-crypto/tink-go/pull/48
- web https://rustsec.org/advisories/RUSTSEC-2026-0125.html
- web https://github.com/advisories/GHSA-fhvh-vw7h-9xf3