Impact
This is a DoS vulnerability that is possible due to a bug in the library that would allow an attacker with specifically designed queries to cause stack overflow panics. Any user with access to the GraphQL handler can send these queries and cause stack overflows. This in turn could potentially compromise the ability of the server to serve data to its users. To make things worse the only mitigation in affected versions creates opportunities for other attacks. This issue is only available if you are using graphql.MaxDepth option in your schema (which is highly recommended in most cases).
Patches
The issue has been patched in version v1.3.0. We have been trying to maintain backwards compatibility and avoid breaking changes so upgrading should not be problematic.
Workarounds
The best workaround is to patch to a version greater than or equal to v1.3.0.
Otherwise, the only workaround in versions prior to v1.3.0 is to disable the graphql.MaxDepth option from your schema. Unfortunately, this could potentially create opportunities for other attacks.
References
There are no references or links. This issue was reported privately and was fixed before creating this Security Advisory.
For more information
If you have any questions or comments feel free to reach out to @pavelnikolov or @tony on the Gopher Slack.
References
jupenur Analyst
Impact
This is a DoS vulnerability that is possible due to a bug in the library that would allow an attacker with specifically designed queries to cause stack overflow panics. Any user with access to the GraphQL handler can send these queries and cause stack overflows. This in turn could potentially compromise the ability of the server to serve data to its users. To make things worse the only mitigation in affected versions creates opportunities for other attacks. This issue is only available if you are using
graphql.MaxDepthoption in your schema (which is highly recommended in most cases).Patches
The issue has been patched in version
v1.3.0. We have been trying to maintain backwards compatibility and avoid breaking changes so upgrading should not be problematic.Workarounds
The best workaround is to patch to a version greater than or equal to
v1.3.0.Otherwise, the only workaround in versions prior to
v1.3.0is to disable thegraphql.MaxDepthoption from your schema. Unfortunately, this could potentially create opportunities for other attacks.References
There are no references or links. This issue was reported privately and was fixed before creating this Security Advisory.
For more information
If you have any questions or comments feel free to reach out to @pavelnikolov or @tony on the Gopher Slack.
References