ash_sql vulnerabilities

A vulnerability in ash_sql allows a caller in a schema-based multitenant application to receive aggregate values computed from another tenant's rows. This occurs when an aggregate is computed over a distinct query, and the outer query is rebuilt without the schema prefix, leading to reads from the default schema instead of the tenant schema.

A vulnerability in ash_sql allows a caller to receive an aggregate value computed over rows a more restrictive filter should have excluded, disclosing counts, sums, or lists across an authorization or tenancy boundary. This occurs because two aggregate queries are considered identical when they differ only in filter, not sort.

A vulnerability in ash_sql allows a user to pad a string field with tab, newline, carriage-return, or form-feed characters and pass a trimmed uniqueness or equality check in the database that the same expression would fail in memory (or the reverse). This occurs because string_trim/1 in SQL removes only spaces, not all whitespace, causing behavioral differences between SQL and memory.

A vulnerability in ash_sql allows a user who supplies a search term to contains/2, string_starts_with/2, or string_ends_with/2 to inject live SQL LIKE wildcards, turning a literal substring search into an attacker-controlled pattern match. This occurs because escape helpers do not escape backslashes, allowing bypass of escaping and activation of wildcards.

A vulnerability in ash_sql allows a caller to bypass a scoping or authorization filter expressed as exists/2 over a relationship that declares both a limit and a parent(...)-referencing filter or sort. In certain cases, the limit and predicate are dropped, causing the check to match any record with any related row.