fix: GraphQL __type introspection bypass via inline fragments when public introspection is disabled (GHSA-q5q9-2rhp-33qw)

[mtrezza]

Pull Request

• Report security issues confidentially.
• Any contribution is under this license.

Issue

GraphQL __type introspection bypass via inline fragments when public introspection is disabled (GHSA-q5q9-2rhp-33qw)

Note: Parse Server 8 sets Apollo's introspection: false directly, which natively blocks __type everywhere — including inline fragments. Parse Server 9 changed this to introspection: true and delegated control to a custom plugin, which is where the gap was introduced.

Tasks

• Add tests
• Add changes to documentation (guides, repository pages, code comments)
• Add security check
• Add new Parse Error codes to Parse JS SDK

Summary by CodeRabbit

• Bug Fixes

  • Improved detection of unauthorized introspection queries in nested query structures.

• Tests

  • Added tests to verify introspection blocking in inline fragments.

[parse-github-assistant]

🚀 Thanks for opening this pull request! We appreciate your effort in improving the project. Please let us know once your pull request is ready for review.

Note

Please respond to review comments from AI agents just like you would to comments from a human reviewer. Let the reviewer resolve their own comments, unless they have reviewed and accepted your commit, or agreed with your explanation for why the feedback was incorrect.

Caution

Pull requests must be written using an AI agent with human supervision. Pull requests written entirely by a human will likely be rejected, because of lower code quality, higher review effort and the higher risk of introducing bugs. Please note that AI review comments on this pull request alone do not satisfy this requirement.

[parseplatformorg]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request enhances GraphQL introspection detection by replacing a root-level-only AST traversal with a recursive function that detects __type fields with arguments anywhere in operation or fragment definitions. Two new tests verify that introspection is blocked when __type is used inside inline fragments without a master key.

Changes

Cohort / File(s)	Summary
Recursive Introspection Detection src/GraphQL/ParseGraphQLServer.js	Refactored hasTypeIntrospection to use a recursive checkSelections helper that traverses nested selection sets instead of only checking root level, enabling detection of __type fields with arguments at any depth in operation definitions.
Introspection Blocking Tests spec/ParseGraphQLServer.spec.js	Added two new test cases verifying that __type introspection inside anonymous and nested inline fragments returns 403 "Introspection is not allowed" when master key is not provided.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• fix: Upgrade to GraphQL Apollo Server 5 and restrict GraphQL introspection #9888: Directly modifies the same hasTypeIntrospection function in ParseGraphQLServer.js to detect __type in nested selections and includes the same test cases.
• fix: Data schema exposed via GraphQL API public introspection (GHSA-48q3-prgv-gm4w) #9819: Enhances GraphQL introspection blocking in ParseGraphQLServer.js through an Apollo plugin configuration mechanism, complementing the detection improvements in this PR.

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description includes the issue (security advisory GHSA-q5q9-2rhp-33qw) and contextual details, but the Approach section is empty and most tasks are unchecked.	Fill in the Approach section with a summary of implementation details. Review and check/uncheck tasks appropriately based on actual work performed.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check	✅ Passed	The title clearly and specifically describes the main change: fixing a GraphQL __type introspection bypass vulnerability in inline fragments when public introspection is disabled, with a security advisory reference.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.68%. Comparing base (c6b7470) to head (f17d506).
⚠️ Report is 2 commits behind head on alpha.

Additional details and impacted files

@@           Coverage Diff           @@
##            alpha   #10111   +/-   ##
=======================================
  Coverage   92.67%   92.68%           
=======================================
  Files         191      191           
  Lines       15872    15879    +7     
  Branches      180      180           
=======================================
+ Hits        14710    14717    +7     
  Misses       1150     1150           
  Partials       12       12           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[parseplatformorg]

🎉 This change has been released in version 9.5.0-alpha.10