SurrealDB versions before 2.0.4 have a vulnerability where field permissions are not properly enforced during SELECT, UPDATE, and DELETE operations. (CVE-2024-58367)
SurrealDB versions before 2.0.4 have a vulnerability where field permissions are not properly enforced during SELECT, UPDATE, and DELETE operations. This allows authorized users to access field values they should not be able to see by exploiting various query techniques such as SELECT VALUE operations, field aliasing, function arguments, WHERE clause filtering, RETURN BEFORE clauses, and SET clause references. The issue leads to unauthorized data disclosure despite lacking explicit SELECT permissions on those fields.
AI Analysis
Technical Summary
SurrealDB versions prior to 2.0.4 fail to enforce field-level permissions correctly across multiple query operations including SELECT, UPDATE, and DELETE. Authorized users can bypass intended access controls and retrieve unauthorized field data by leveraging query constructs like SELECT VALUE, aliasing fields, passing fields as function arguments, filtering with WHERE clauses, using RETURN BEFORE clauses, and referencing fields in SET clauses. This vulnerability is tracked as CVE-2024-58367 and is categorized under CWE-285 (Improper Authorization). No patch or remediation details are provided in the available data.
Potential Impact
The vulnerability allows authorized users to access and leak field values they are not authorized to view, violating data confidentiality controls within SurrealDB. This could lead to unauthorized disclosure of sensitive information stored in protected fields. The flaw affects the integrity of access control enforcement at the field level during database query operations.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict database user permissions to the minimum necessary and monitor for unusual query patterns that might exploit this weakness. Avoid granting broad SELECT, UPDATE, or DELETE permissions to users who do not require them.
SurrealDB versions before 2.0.4 have a vulnerability where field permissions are not properly enforced during SELECT, UPDATE, and DELETE operations. (CVE-2024-58367)
Description
SurrealDB versions before 2.0.4 have a vulnerability where field permissions are not properly enforced during SELECT, UPDATE, and DELETE operations. This allows authorized users to access field values they should not be able to see by exploiting various query techniques such as SELECT VALUE operations, field aliasing, function arguments, WHERE clause filtering, RETURN BEFORE clauses, and SET clause references. The issue leads to unauthorized data disclosure despite lacking explicit SELECT permissions on those fields.
CVSS v4.0
Affected software
pkg:github/surrealdb/surrealdbRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
SurrealDB versions prior to 2.0.4 fail to enforce field-level permissions correctly across multiple query operations including SELECT, UPDATE, and DELETE. Authorized users can bypass intended access controls and retrieve unauthorized field data by leveraging query constructs like SELECT VALUE, aliasing fields, passing fields as function arguments, filtering with WHERE clauses, using RETURN BEFORE clauses, and referencing fields in SET clauses. This vulnerability is tracked as CVE-2024-58367 and is categorized under CWE-285 (Improper Authorization). No patch or remediation details are provided in the available data.
Potential Impact
The vulnerability allows authorized users to access and leak field values they are not authorized to view, violating data confidentiality controls within SurrealDB. This could lead to unauthorized disclosure of sensitive information stored in protected fields. The flaw affects the integrity of access control enforcement at the field level during database query operations.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict database user permissions to the minimum necessary and monitor for unusual query patterns that might exploit this weakness. Avoid granting broad SELECT, UPDATE, or DELETE permissions to users who do not require them.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-j9rh-f527-3x87
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2024-58367"]
- Ecosystems
- []
- Database Specific Severity
- HIGH
- Cvss Version
- 4.0
Threat ID: 6a5ba17e44ab8fbf7c789b92
Added to database: 07/18/2026, 15:53:34 UTC
Last enriched: 07/18/2026, 16:22:07 UTC
Last updated: 07/18/2026, 18:59:14 UTC
Views: 8
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.