Incomplete redaction re-attaches the original error path in AshGraphql, leaking internal field names
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 1.11.0 and 78e90d369f09f44c534816de541e60841066a467.
Generation of Error Message Containing Sensitive Information vulnerability in ash-project ash_graphql allows a remote client to read internal field names that an application configured its error_handler to redact. In AshGraphql.Errors, each error is passed to the configured error_handler and the returned map is merged with the pre-handler path via Map.put_new(handled, :path, path). Because put_new defers to the handler only when the handler itself set :path, a sanitizing handler that returns a fresh map or deletes :path has that decision reverted. The re-injected path comes from build_error_path/5, which falls back to raw internal Ash attribute and argument names when no field_names mapping is configured. A validation failure on a non-exposed or nested field therefore returns internal names in the GraphQL error path, defeating the application's redaction. This issue affects ash_graphql: from 1.9.0 before 1.11.0.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| ash-project | >=1.9.0 <1.11.0, >=6d2d8d995906d68cc245d209a9b3f9853405eb61 <78e90d369f09f44c534816de541e60841066a467 | 1.11.0, 78e90d369f09f44c534816de541e60841066a467 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket