Vulnerability in surrealdb (CVE-2024-58358)
Summary
Vulnerability in surrealdb (CVE-2024-58358). Risk of unauthorized operations or information disclosure. Exploitable via Ident. Mitigation: upgrade to 2.1.0 or later.
Original description
The description as published by the source.
SurrealDB versions before 2.1.0 contain a denial of service vulnerability in role conversion that allows privileged owner users to define users with nonexistent roles. Attackers can trigger an uncaught panic by signing in with a user assigned an invalid role, crashing the server.
Source: NIST National Vulnerability Database NVD GitHub Advisory
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-58358 has been found in surrealdb.
Attackers can target a specific entry point like Ident over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.9/10.
What to do: upgrade surrealdb to 2.1.0 or later.
If unsure, ask your IT team or search "surrealdb CVE-2024-58358" on the vendor's site.
CVE-2024-58358 (surrealdb) — CWE-248 / CVSS v3 4.9
Attack vector: remote (network-reachable) / no user interaction
Attack surface: Ident / Role / owner / editor
Patched: 2.1.0 — apply immediately
Workaround: Affected users who are unable to update may want to limit access to users with the owner role at any level to trusted parties only.
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-248) exists in surrealdb. Attackers reach the vulnerable code path via Ident.
Check the vendor advisory for the affected versions of surrealdb. Attack surface: Ident / Role / owner / editor.
Severity: Medium (CVSS 4.9/10). Risk of unauthorized operations or information disclosure.
Update to 2.1.0.
Workaround: Affected users who are unable to update may want to limit access to users with the owner role at any level to trusted parties only.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'surrealdb' . 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 'surrealdb' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
surrealdbを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Affected users who are unable to update may want to limit access to users with the `owner` role at any level to trusted parties only.パッチが適用されるまでの応急処置として、Affected users who are unable to update may want to limit access to users with the
ownerrole at any level to trusted parties only. を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade surrealdb to 2.1.0ステージング環境で 2.1.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory vulncheck.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com