Attack Chain

1. An attacker crafts a GraphQL query with a large number of nested inline fragments.
2. The query is submitted to a webonyx/graphql-php application.
3. The DocumentValidator::validate() function invokes the default rules, including OverlappingFieldsCanBeMerged.
4. Within OverlappingFieldsCanBeMerged.php, the internalCollectFieldsAndFragmentNames function flattens inline fragments into the parent $astAndDefs map, increasing the size of the map.
5. The collectConflictsWithin function iterates through the flattened fields, performing an O(n^2) pairwise comparison of fields.
6. The findConflict function is recursively called for sub-selections, compounding the cost to O(n^2 x m^2).
7. Due to the absence of a comparison budget or validation timeout, the validation process consumes excessive CPU resources.
8. The PHP worker process becomes pinned, leading to potential denial of service via worker pool exhaustion.

Impact

A successful attack can lead to a denial of service (DoS) due to the exhaustion of server resources. A single 364 KB query can consume 117 seconds of CPU time, potentially exhausting the php-fpm worker pool. Systems with default configurations, such as Lighthouse/Laravel deployments, may be vulnerable even with max_execution_time limits, as the worker may burn significant CPU time before being terminated. Exploitation can bypass body-size limits and WAF rules via gzip compression, as the decompressed payload is much larger than the compressed one. The vulnerability affects all applications using the standard validation pipeline in webonyx/graphql-php versions prior to 15.32.2.

Recommendation

• Upgrade to webonyx/graphql-php version 15.32.2 or later, which includes a fix that addresses this vulnerability.
• Implement a comparison budget in OverlappingFieldsCanBeMerged to limit the number of comparisons performed during validation, as described in the remediation options.
• Consider capping inline-fragment flattening in internalCollectFieldsAndFragmentNames to prevent excessive growth of the $astAndDefs map, as outlined in the remediation options.
• Deploy the Sigma rule Detect GraphQL PHP Excessive Validation Time to identify potential exploitation attempts by monitoring the execution time of GraphQL validation processes.