CVE-2024-58362: Surrealdb vulnerability (CVSS 8.8)

Description

SurrealDB before 1.5.5 (and 2.0.0-beta before 2.0.0-beta.3) accepts an arbitrary object in the signin and signup operations of the RPC API without recursively validating it for non-computed values. When a record access method defines a SIGNIN or SIGNUP query and the RPC API is exposed to untrusted users, an unauthenticated attacker can encode a binary object containing a subquery using the bincode serialization format and supply it in place of credentials. The subquery is then executed within the database owner's SIGNIN/SIGNUP query under a system user session with the editor role, allowing the attacker to select, create, update, and delete non-IAM resources (though not view the query results directly, and not affect IAM resources, which require the owner role).

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredLow

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

Surrealdb< 1.5.5 · 2.0.0

Remediation

Fixed in

Surrealdb≥ 1.5.5

Patch & vendor advisories

https://github.com/surrealdb/surrealdb/security/advisories/GHSA-64f8-pjgr-9wmr

References

https://github.com/surrealdb/surrealdb/security/advisories/GHSA-64f8-pjgr-9wmrVendor Advisory
https://www.vulncheck.com/advisories/surrealdb-before-query-injection-via-rpc-apiThird Party Advisory

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2024-58362 being actively exploited?

CVE-2024-58362 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.64%.

How severe is CVE-2024-58362?

CVE-2024-58362 has a CVSS 3.1 base score of 8.8, rated high. EPSS estimates a 0.64% probability of exploitation.

Which products are affected by CVE-2024-58362?

Affected products include Surrealdb.

How do I fix CVE-2024-58362?

Upgrade affected software to a fixed version, for example Surrealdb 1.5.5 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2024-58362 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo