← Back
GHSA-22w3-693w-x895
Vulnerability in webauthn-rs-core (GHSA-22w3-693w-x895)
Summary
vulnerability in webauthn-rs-core (GHSA-22w3-693w-x895). Risk of unauthorized operations or information disclosure. Exploitable via ``Origin``. Mitigation: upgrade to `0.6.1-dev` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-22w3-693w-x895** has been found in webauthn-rs-core.
Attackers can target a specific entry point like ``Origin`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade webauthn-rs-core to **0.6.1-dev** or later.
If unsure, ask your IT team or search "webauthn-rs-core GHSA-22w3-693w-x895" on the vendor's site.
GHSA-22w3-693w-x895 (webauthn-rs-core) — CWE-1289 /
Attack surface: `Origin` / `CollectedClientData` / `crab.example` / `true`
Patched: `0.6.1-dev` — 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-1289) exists in webauthn-rs-core. Attackers reach the vulnerable code path via ``Origin`` without authentication.
📍 Affected scope
webauthn-rs-core — . Attack surface: `Origin` / `CollectedClientData` / `crab.example` / `true`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.6.1-dev**.
🛡️ 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 'webauthn-rs-core' .` 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 'webauthn-rs-core' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `webauthn-rs-core` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade webauthn-rs-core to 0.6.1-devステージング環境で 0.6.1-dev に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
crates.io
webauthn-rs-core
[{"type":"SEMVER","events":[{"introduced":"0.6.0-dev"},{"fixed":"0.6.1-dev"}]}]
crates.io
webauthn-authenticator-rs
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.5.5"}]}]