Am I affected?

type your ash_graphql version to check

Description

Incorrect Authorization vulnerability in ash-project ash_graphql allows an authenticated subscriber in one tenant to receive another tenant's records over GraphQL subscriptions.

The subscription resolver in AshGraphql.Graphql.Resolver authorizes each notification payload in memory: its fast path calls Ash.can/3 with run_queries?: false, which evaluates the read policy filter against the in-memory record via Ash.Expr.eval/2 and never issues a query. Ash applies multitenancy at query-build and data-layer-prefix time, not inside query.filter, so the evaluated policy carries no tenant condition and a tenant-B notification routed to a tenant-A subscriber is emitted whenever the policy filter is true. The single-notification clause has no tenant guard at all, and the batched clause checks only the head of the notification list, so non-head entries authorize purely in memory. A tenant-scoped read is reached only when filter evaluation fails.

This issue affects ash_graphql: from 1.4.0 before 1.11.0.

Weaknesses & attack patterns

Weakness

CWE-863 · Incorrect Authorization in catalog → MITRE ↗

Attack patterns

CAPEC-1 · Accessing Functionality Not Properly Constrained by ACLs MITRE ↗

Affected — Hex / ash_graphql Hex.pm ↗ Repository ↗

≥ 1.4.0 < 1.11.0 affected
every other version: unaffected
cpe cpe:2.3:a:ash-project:ash_graphql:*:*:*:*:*:*:*:*
version type semver
modules · source files · routines
modules 'Elixir.AshGraphql.Graphql.Resolver'
source files lib/graphql/resolver.ex
routines 'Elixir.AshGraphql.Graphql.Resolver':resolve/2

Affected — GitHub / ash-project/ash_graphql Repository ↗

≥ 4c377e5 < 6e30b8b affected
every other version: unaffected
cpe cpe:2.3:a:ash-project:ash_graphql:*:*:*:*:*:*:*:*
version type git
modules · source files · routines
modules 'Elixir.AshGraphql.Graphql.Resolver'
source files lib/graphql/resolver.ex
routines 'Elixir.AshGraphql.Graphql.Resolver':resolve/2

Configurations

The application exposes ash_graphql subscriptions on a multitenant resource whose read policy passes on in-memory filter evaluation alone, and where a notification created in one tenant can reach a subscriber scoped to another tenant.

References

Credits

Peter Ullrich Finder Reporter
Jonatan Männchen / EEF Coordinator
Zach Daniel / Ash Project Remediation developer

CVSS breakdown

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitability

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None

Vulnerable System

Confidentiality
High
Integrity
None
Availability
None

Subsequent Systems

Confidentiality
None
Integrity
None
Availability
None
« All CVEs