Versions of the package graphql from 16.3.0 and before 16.8.1 are vulnerable to Denial of Service (DoS) due to insufficient checks in the OverlappingFieldsCanBeMergedRule.ts file when parsing large queries. This vulnerability allows an attacker to degrade system performance. Note: It was not proven that this vulnerability can crash the process.
The product does not properly control the allocation and maintenance of a limited resource.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Graphql | Graphql | 16.3.0 (including) | 16.8.1 (excluding) |
| Graphql | Graphql | 17.0.0-alpha1 (including) | 17.0.0-alpha1 (including) |
| Graphql | Graphql | 17.0.0-alpha2 (including) | 17.0.0-alpha2 (including) |
| Migration Toolkit for Virtualization 2.5 | RedHat | migration-toolkit-virtualization/mtv-console-plugin-rhel9:2.5.2-5 | * |
| Red Hat Advanced Cluster Security 4.4 | RedHat | advanced-cluster-security/rhacs-main-rhel8:4.4.0-17 | * |
| Node-graphql | Ubuntu | bionic | * |
| Node-graphql | Ubuntu | lunar | * |
| Node-graphql | Ubuntu | mantic | * |
| Node-graphql | Ubuntu | oracular | * |
| Node-graphql | Ubuntu | trusty | * |
| Node-graphql | Ubuntu | xenial | * |
Mitigation of resource exhaustion attacks requires that the target system either:
The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question.
The second solution is simply difficult to effectively institute – and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.