← Back
GHSA-2cgv-28vr-rv6j
Information Disclosure in libcrux-intrinsics (GHSA-2cgv-28vr-rv6j)
Summary
vulnerability in libcrux-intrinsics (GHSA-2cgv-28vr-rv6j). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `0.0.4` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-2cgv-28vr-rv6j** has been found in libcrux-intrinsics.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade libcrux-intrinsics to **0.0.4** or later.
If unsure, ask your IT team or search "libcrux-intrinsics GHSA-2cgv-28vr-rv6j" on the vendor's site.
GHSA-2cgv-28vr-rv6j (libcrux-intrinsics) — CWE-200 /
Patched: `0.0.4` — 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
**information disclosure** (CWE-200) exists in libcrux-intrinsics.
📍 Affected scope
libcrux-intrinsics — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.0.4**.
🛡️ 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-intrinsics' .` 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-intrinsics' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `libcrux-intrinsics` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade libcrux-intrinsics to 0.0.4ステージング環境で 0.0.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
rust
libcrux-intrinsics
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.0.4"}]}]
rust
libcrux-ml-kem
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.0.4"}]}]
rust
libcrux-ml-dsa
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.0.4"}]}]