Skip to content
surrealdbGHSA-q3gg-m8hr-h4x4

Externally Controlled Format String in Scripting Functions

High8.5CVE-2024-58366 · Published Feb 21, 2024 · updated Jul 19, 2026

GitHub advisory

Affected versions

PackageAffectedFixed in
surrealdb
crates.io
< 1.1.11.1.1
Details and references

The `rquickjs` crate used by SurrealDB implements Rust bindings to the QuickJS C library and is used to execute SurrealDB scripting functions. The `rquickjs` function `Exception::throw_type` takes a string and returns an error object. Prior to version `0.4.2` of the crate, this string would be fed directly into `printf`, which will receive the error string as a format string with no additional arguments, leading to undefined behavior. This issue triggers when a SurrealDB scripting function returns an error and its input contains a format string such as `%s` or `%d`. This vulnerability can only affect SurrealDB servers explicitly enabling the scripting capability with `--allow-scripting` or `--allow-all` and equivalent environment variables `SURREAL_CAPS_ALLOW_SCRIPT=true` and `SURREAL_CAPS_ALLOW_ALL=true`. ### Impact An attacker with privileges to execute scripting functions with arbitrary inputs may be able to exploit this format string vulnerability in order read arbitrary memory from the remote SurrealDB process. A format string vulnerability may also be further exploited to execute arbitrary code with the privileges of the SurrealDB process. The fact that error messages are limited to 256 bytes coupled with [exploit mitigation features supported in Rust executables](https://doc.rust-lang.org/rustc/exploit-mitigations.html#exploit-mitigations-1) may somewhat increase the complexity of exploiting this vulnerability to reliably achieve remote code execution in practice. ### Patches - Version 1.1.1 and later are not affected by this issue. ### Workarounds Users unable to update should restrict access from untrusted users to define and execute scripting functions. This can be achieved by removing the scripting capability by default or with `--deny-scripting` and equivalent environment variable `SURREAL_CAPS_DENY_SCRIPT=true`. If not possible, network access should be limited to trusted users. ### References - https://github.com/surrealdb/surrealdb/issues/3327 - https://github.com/surrealdb/surrealdb/pull/3332 - https://github.com/DelSkayn/rquickjs/pull/247

CVSS 3.1
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
Severity from
GitHub (reviewed advisory)
Also known as
CVE-2024-58366

More surrealdb advisories

All
DateAdvisory
Feb 212024Uncaught Exception Handling Parsing Errors on Line Terminators
CVE-2024-58364Medium6.5fixed in 1.2.1
Feb 212024Uncaught Exception in Macro Expecting Native Function to Exist
CVE-2024-58365Medium6.5fixed in 1.2.0
Jan 192024SurrealDB vulnerable to Uncontrolled CPU Consumption via WebSocket Interface
GHSA-58j9-j2fj-v8f4High7.5fixed in 1.1.0
Jan 182024Uncontrolled Recursion in SurrealQL Parsing
CVE-2024-58370Medium6.5fixed in 1.1.0
Jan 182024Uncaught Exception processing HTTP Headers in SurrealDB
CVE-2024-58368High7.5fixed in 1.1.0
Jan 182024Uncaught Exception in surrealdb
CVE-2024-58369Medium6.5fixed in 1.1.1

Critical advisories by email

Wednesdays: the week’s critical and high advisories in the AI and data stack, with the fixed versions. Only in weeks that have some.

Double opt-in. Unsubscribe any time.