Skip to content
SurrealDBGHSA-m24x-r6q3-2vp9

Uncaught Exception processing HTTP Headers in SurrealDB

High7.5CVE-2024-58368 · Published Jan 18, 2024 · updated Sep 4, 2026

The `ID`, `DB` and `NS` headers accepted by the SurrealDB HTTP REST API would fail to parse when containing some special characters. This would cause a panic which would crash the SurrealDB server, leading to denial of service. This issue only affects the SurrealDB binary; it does not affect the SurrealDB library. ### Impact An unauthenticated client may issue an HTTP request to the SurrealDB HTTP REST API containing one of the affected headers with values containing special characters in order to crash the SurrealDB server. This does not require the SurrealDB server to be running with any specific capabilities other than exposing the affected interface. ### Patches - Version 1.1.0 and later are not affected by this issue. ### Workarounds Concerned users unable to update may want to limit untrusted access to the SurrealDB HTTP REST API unless such access is required by the application. To limit the impact of the denial of service, SurrealDB administrators may also want to ensure that the SurrealDB process is running so that it can be automatically re-started after a crash. ### Resources - #2985 ([diff](https://github.com/surrealdb/surrealdb/pull/2985/files#diff-7ad06ddbb88...

GitHub advisory

Affected versions

PackageAffectedFixed in
surrealdb
crates.io
< 1.1.01.1.0
Details and references

The `ID`, `DB` and `NS` headers accepted by the SurrealDB HTTP REST API would fail to parse when containing some special characters. This would cause a panic which would crash the SurrealDB server, leading to denial of service. This issue only affects the SurrealDB binary; it does not affect the SurrealDB library. ### Impact An unauthenticated client may issue an HTTP request to the SurrealDB HTTP REST API containing one of the affected headers with values containing special characters in order to crash the SurrealDB server. This does not require the SurrealDB server to be running with any specific capabilities other than exposing the affected interface. ### Patches - Version 1.1.0 and later are not affected by this issue. ### Workarounds Concerned users unable to update may want to limit untrusted access to the SurrealDB HTTP REST API unless such access is required by the application. To limit the impact of the denial of service, SurrealDB administrators may also want to ensure that the SurrealDB process is running so that it can be automatically re-started after a crash. ### Resources - #2985 ([diff](https://github.com/surrealdb/surrealdb/pull/2985/files#diff-7ad06ddbb88d77138e5daf40a0dac5443d78947acd69a284a7c2bceb61f9c5f0L83-R119))

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

More SurrealDB advisories

All SurrealDB
Advisory
Uncaught Exception in Macro Expecting Native Function to Exist
Medium6.5Feb 21, 2024
Uncaught Exception Handling Parsing Errors on Line Terminators
Medium6.5Feb 21, 2024
SurrealDB vulnerable to Uncontrolled CPU Consumption via WebSocket Interface
High7.5Jan 19, 2024
Uncontrolled Recursion in SurrealQL Parsing
Medium6.5Jan 18, 2024
Uncaught Exception in surrealdb
Medium6.5Jan 18, 2024
SurrealDB: Full Table Permissions by Default
High8.8Dec 15, 2023

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.