همهٔ گزارش‌ها
متوسط

Parse Server's GraphQL "Did you mean ...?" validation suggestions disclose schema to unauthenticated callers

متن اصلی

نسخه‌های متأثر

نسخه‌های متأثر
< 8.6.78
نسخهٔ اصلاح‌شده
8.6.78
نسخه‌های متأثر
>= 9.0.0, < 9.9.1-alpha.2
نسخهٔ اصلاح‌شده
9.9.1-alpha.2

بهره‌برداری

CVE-2026-47248

احتمال بهره‌برداری در ۳۰ روز آینده: 0.29%

FIRST EPSS · ۱۴۰۵/۰۸/۳۰

شرح آسیب‌پذیری

Impact

Parse Server's GraphQL endpoint discloses schema metadata to unauthenticated callers through Did you mean ...? suggestions embedded in GraphQL validation-error messages. An unauthenticated caller who knows only the public application id can iteratively send malformed queries to reconstruct class names, field names, argument names, mutation names, and input-object fields. This bypasses the IntrospectionControlPlugin enforced when graphQLPublicIntrospection: false (the default) and defeats the schema-hiding goal of prior advisories GHSA-48q3-prgv-gm4w and GHSA-q5q9-2rhp-33qw. Schema disclosure aids reconnaissance for downstream authorization probing but does not by itself leak object data or authentication material.

Patches

A new SchemaSuggestionsControlPlugin Apollo plugin strips the Did you mean ...? suffix from GraphQL validation-error messages during validationDidStart, which runs before any introspection gate. The plugin applies only when graphQLPublicIntrospection: false and the caller is not a master-key or maintenance-key holder, matching the trust model of the existing IntrospectionControlPlugin.

Workarounds

No code workaround is available short of disabling the GraphQL API (mountGraphQL: false). Operators who require disclosure-resistant validation errors should upgrade to a patched release.

Resources

پیوندها

گزارش‌دهندگان

  • offset
  • mtrezza