Parse Server 9.0.0 Information Disclosure via GraphQL Error Messages
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 8.6.86 and 9.10.0-alpha.5.
Parse Server versions >= 9.0.0 before 9.10.0-alpha.5 and >= 8.2.2 before 8.6.86 return GraphQL validation error messages that name required custom input fields even when public introspection is disabled (graphQLPublicIntrospection: false, the default). A client holding only the public application id — with no user session, master key, or maintenance key — can trigger validation errors to learn the names of required (non-null) custom fields on classes it already references by name, partially defeating the schema-hiding intent of disabling public introspection. No stored data, credentials, optional field names, unreferenced class names, or Cloud Code function names are exposed.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| parse-community | >=8.2.2 <8.6.86, >=9.0.0 <9.10.0-alpha.5 | 8.6.86, 9.10.0-alpha.5 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket