CVE-2024-58363GHSA-GH9F-6XM2-C4J2
SurrealDB before 1.5.4 Authentication Bypass via Database Switch
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.5.4, 2.0.0-alpha.6, 1.5.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
SurrealDB before 1.5.4 and 2.0.0-alpha.1 before 2.0.0-alpha.6 fails to properly validate authentication when a scope user switches databases using the USE clause or use method. Attackers with an authenticated session can impersonate an unrelated user in a different database if a user record with an identical identifier exists, allowing unauthorized actions if permissions rely solely on the $auth parameter.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- surrealdb surrealdb
fixed in 1.5.4
- surrealdb surrealdb
From 2.0.0-alpha.1 · fixed in 2.0.0-alpha.6
- surrealdb surrealdb-core
fixed in 1.5.1
- surrealdbcrates.io
fixed in 1.5.4
- surrealdbcrates.io
From 2.0.0-alpha.1 · fixed in 2.0.0-alpha.6
- surrealdb-corecrates.io
fixed in 1.5.1