Vulnerability in odoh-rs (CVE-2023-3766)
Summary
Vulnerability in odoh-rs (CVE-2023-3766). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.0.2 or later.
Original description
The description as published by the source.
A vulnerability was discovered in the odoh-rs rust crate that stems from faulty logic during the parsing of encrypted queries. This issue specifically occurs when processing encrypted query data received from remote clients and enables an attacker with knowledge of this vulnerability to craft and send specially designed encrypted queries to targeted ODOH servers running with odoh-rs. Upon successful exploitation, the server will crash abruptly, disrupting its normal operation and rendering the service temporarily unavailable.
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-2023-3766 has been found in odoh-rs.
Risk of unauthorized operations or information disclosure.
What to do: upgrade odoh-rs to 1.0.2 or later.
If unsure, ask your IT team or search "odoh-rs CVE-2023-3766" on the vendor's site.
CVE-2023-3766 (odoh-rs) — CWE-120
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.0.2 — 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.
A vulnerability (CWE-120) exists in odoh-rs.
Check the vendor advisory for the affected versions of odoh-rs.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.0.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'odoh-rs' . 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
-
1Identify exposure identify
grep -r 'odoh-rs' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
odoh-rsを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade odoh-rs to 1.0.2ステージング環境で 1.0.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory rustsec.org
- advisory github.com
- package github.com
- package crates.io
- patch github.com
- web github.com