GHSA-6wr5-jmpr-mjcx

Suggest an improvement
Source
https://github.com/advisories/GHSA-6wr5-jmpr-mjcx
Import Source
https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2024/02/GHSA-6wr5-jmpr-mjcx/GHSA-6wr5-jmpr-mjcx.json
JSON Data
https://api.osv.dev/v1/vulns/GHSA-6wr5-jmpr-mjcx
Published
2024-02-21T00:03:06Z
Modified
2024-02-21T00:03:06Z
Severity
  • 6.5 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H CVSS Calculator
Summary
Uncaught Exception in Macro Expecting Native Function to Exist
Details

The query executor would panic when executing a query containing a call to a built-in SurrealDB function that did not exist. This could occur accidentally in situations where the version of the SurrealDB client was newer than the SurrealDB server or when a pre-parsed query was provided to the server via a newer version of the SurrealDB SDK.

Impact

A client that is authorized to run queries in a SurrealDB server is able to craft and execute a pre-parsed query invoking a nonexistent built-in function, which will cause a panic. This will crash the server, leading to denial of service.

Patches

  • Version 1.2.0 and later are not affected by this issue.

Workarounds

Concerned users unable to update may want to limit the ability of untrusted users to run arbitrary SurrealQL queries in the affected versions of SurrealDB. 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.

References

  • #3454
  • https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=65755
Database specific
{
    "nvd_published_at": null,
    "cwe_ids": [
        "CWE-248"
    ],
    "severity": "MODERATE",
    "github_reviewed": true,
    "github_reviewed_at": "2024-02-21T00:03:06Z"
}
References

Affected packages

crates.io / surrealdb

Package

Affected ranges

Type
SEMVER
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
1.2.0

Database specific

{
    "last_known_affected_version_range": "<= 1.1.1"
}