Vulnerability in surrealdb (CVE-2024-58357)
Summary
Vulnerability in surrealdb (CVE-2024-58357). Risk of unauthorized operations or information disclosure. Exploitable via timestamp_opt. Mitigation: upgrade to 2.1.0 or later.
Original description
The description as published by the source.
SurrealDB versions before 2.1.0 contain an uncaught exception vulnerability in the rand::time() function that panics when unwrap is called on a None result from timestamp_opt. Authorized clients can repeatedly invoke rand::time() to reliably trigger server panics and cause denial of service.
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-58357 has been found in surrealdb.
Attackers can target a specific entry point like timestamp_opt over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.5/10.
What to do: upgrade surrealdb to 2.1.0 or later.
If unsure, ask your IT team or search "surrealdb CVE-2024-58357" on the vendor's site.
CVE-2024-58357 (surrealdb) — CWE-248 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: timestamp_opt / chrono / None / unwrap
Patched: 2.1.0 — apply immediately
Workaround: Affected users who are unable to update may want to limit the ability of untrusted clients to run the rand::time() function in the affected versions of SurrealDB using security capabilities.
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 timestamp_opt.
Check the vendor advisory for the affected versions of surrealdb. Attack surface: timestamp_opt / chrono / None / unwrap.
Severity: Medium (CVSS 6.5/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 the ability of untrusted clients to run the rand::time() function in the affected versions of SurrealDB using security capabilities.
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 the ability of untrusted clients to run the `rand::time()` function in the affected versions of SurrealDB using security capabilities.パッチが適用されるまでの応急処置として、Affected users who are unable to update may want to limit the ability of untrusted clients to run the
rand::time()function in the affected versions of SurrealDB using security capabilities. を実施。回避策の副作用 (機能低下) を確認した上で。 -
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