GraphQL is an open-source data query and manipulation language that can be used to build application program interfaces (APIs). Since its initial inception by Facebook in 2012 and subsequent release in 2015, GraphQL has grown steadily in popularity. [Some estimate]() that by 2025, more than 50% of enterprises will use GraphQL in production, up from less than 10% in 2021.
Unlike Rest APIs, which return information called from an endpoint and require the user to extract applicable information, GraphQL allows the user to query specific data from a GraphQL schema and return precise results.
Although GraphQL is relatively new and allows you to query exactly what you require, it is still prone to the same common vulnerabilities as other APIs. There are weaknesses that attackers can exploit to gain access to sensitive data, making securing GraphQL extremely important. The ability to scan a GraphQL schema will help to remediate those weaknesses and provide additional API security coverage.
## Why GraphQL security is important
While there are numerous benefits to adopting GraphQL, the security implications are less well-understood. Can functionality be abused? What problems come with querying flexibility? Which vulnerabilities can be exploited? These are all points of concern for its use base.
GraphQL is also no different from other APIs in terms of potential attack vectors. Indeed, it has its own unique security vulnerabilities on top of those you would encounter through a REST API.
As we discussed in our recent post on [API security best practices](), APIs are a lucrative target that can allow hackers to gain access to an otherwise secure system and exploit vulnerabilities. Not only do APIs often suffer from the same vulnerabilities as web applications â like broken access controls, injections, security misconfigurations, and vulnerabilities inherited from other dependent code libraries â but they are also more susceptible to resource consumption and rate limiting issues due to the automated nature of their users.
## Best practices for securing GraphQL
The first step in securing your GraphQL endpoint is to familiarize yourself with some of the most common vulnerabilities and best practices to protect against potential exposure. The most common are injection vulnerabilities â such as [SQL injection](), OS command injection, and [server-side request forgery]() â where the data provided in the arguments of a GraphQL request is injected into commands, queries, and other executable entities by the application code. Other common vulnerabilities include a lack of resource management that can enable a [Denial of Service (DoS)]() attack, due to general graph/query complexity and the potential for large batch requests. Finally, broken access control vulnerabilities exist in GraphQL APIs in much the same way as in other applications and services, but they can be exacerbated by the segmented nature of GraphQL query resolvers.
There are several best practice recommendations which can be utilized to counter such attacks.
* **Only allow valid values to be passed** – Values should be controlled via allow lists, custom validators and correct definitions.
* **Depth limiting** – Restricting the depth of a query only to predetermined levels will allow control over the expense of a query and avoid tying up your back end unnecessarily.
* **Amount limiting** – Restricting the amount of a particular object in a query will reduce the expense of the query by not allowing more than x objects to be called.
* **Query cost analysis** – Checking how expensive a query may be before you allow it to run is a useful additional step to block expensive or malicious queries.
* **Control input rejections** – Ensure you donât overly expose information about the API during input rejections.
* **Introspection turned off** – By default, introspection will be enabled on GraphQL, but simply disabling introspection will restrict what information the consumer can access and not allow them to learn everything about your API.
OWASP have also produced a really neat [cheat sheet series](), which provides an introduction to GraphQL, as well as a detailed rundown of best practices and common GraphQL attacks, to help teams with upskilling and securing GraphQL.
## How to secure GraphQL
The second step in securing your GraphQL endpoint is right here with Rapid7! While almost every modern [DAST]() solution can properly parse and understand requests to and responses from web applications and, in most cases, APIs, that doesnât mean all those tools will specifically understand GraphQL. Thatâs why [InsightAppSec]() has specifically added support for parsing GraphQL requests, responses, and schemas, so that it can properly scan GraphQL-based APIs. This new feature provides customers with the ability to scan GraphQL endpoints to identify and then remediate any vulnerabilities encountered.
Initial support will be provided to identify the following vulnerabilities:
* SQL injection
* Blind SQL injection
* OS commanding
* Server-side request forgery
* Local file inclusion/remote file inclusion
To find out how to execute a GraphQL scan, check out our [doc on the feature]() in InsightAppSec for additional information, support, and guidance.Read More