AshAi aggregate tool can read field-policy-protected fields
ash-project ash_ai
ash-project ash_ai
| Product | Affected | Fixed in |
|---|---|---|
| ash-project ash_ai |
| No fix yet |
| ash-project ash_ai |
| No fix yet |
AshAi exposes Ash read actions to language-model tool calls. The read tool accepts an aggregate result type (min, max, sum, avg) that builds an ad-hoc Ash.Query.Aggregate over a named field and returns its raw value.
Ash field policies redact forbidden fields on returned records (replacing them with %Ash.ForbiddenField{}), but that redaction does not apply to aggregate values. A tool caller could therefore read a field the calling actor's field policies forbid by requesting it as an aggregate; min/max in particular return an actual field value. This includes fields that are public? true but restricted per-actor by a field policy, such as sensitive PII. The tool's existing check only required the field to be public, which is a separate axis from per-actor field-policy authorization.
The fix authorizes the aggregated field against the resource's field policies, so aggregating over a field the actor may not see is refused or scoped to the rows where it is visible.
This issue affects ash_ai: from 0.1.0 before 1.0.3.
From the CVE record · EEF
AshAi read tools allow language-model tool callers to request aggregate values for fields they cannot see under the calling actor's field policies. When a field is public but restricted for that actor, aggregates bypass record redaction; min and max can return an actual field value. The input does not specify whether authentication or user interaction is required.
Teams running ash_ai versions 0.1.0 through versions before 1.0.3 should check their deployments.