CyberRota Analysis
AI-GeneratedThe ash_sql library contains an incorrect authorization vulnerability that allows unauthorized users to access aggregate values, potentially disclosing sensitive data across authorization or tenancy boundaries. This flaw arises from the mishandling of aggregate queries with identical names but different filters, leading to the exposure of counts, sums, or lists that should have been restricted. Organizations using ash_sql versions from 0.1.0 to before 0.7.1 should prioritize remediation to safeguard against potential data leaks.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
Incorrect Authorization vulnerability in ash-project 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. AshSql.Aggregate.different_queries?/2 reports two aggregate queries as different only when their filter and their sort both differ. Aggregate queries rarely carry a sort, so two aggregates that share a name but carry entirely different filters compare as identical. The colliding aggregate keeps its name and is treated as already computed, and select_aggregates returns the first-registered variant's value. The same name reaches the builder twice with different filters when actor or tenant context is stamped into each aggregate's query, so a narrowly filtered aggregate can be served the value of a previously registered broad one. This issue affects ash_sql: from 0.1.0 before 0.7.1.