GraphQL security best practices - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Query Depth Limiting

Why is limiting the depth of GraphQL queries important for security?

A To allow users to fetch unlimited data without restrictions

B To prevent attackers from sending deeply nested queries that can overload the server

C To increase the speed of query execution by caching results

D To enable clients to bypass authentication checks

💡 Hint

Think about how complex queries affect server resources.

Limiting query depth helps prevent denial-of-service attacks by stopping very deep nested queries that consume excessive server resources.

❓ query_result

intermediate

Effect of Missing Authorization Checks

Given a GraphQL API without authorization checks on sensitive fields, what is the likely output when an unauthorized user queries those fields?

GraphQL

query {
  user(id: "123") {
    id
    email
    secretData
  }
}

A The query returns an error and no data

B The query returns only id and email, secretData is null

C The query returns only id, email, and a warning message

D The query returns all requested fields including secretData

💡 Hint

Consider what happens if no checks block access.

If authorization is missing, the server will return all requested data, including sensitive fields, exposing secrets to unauthorized users.

📝 Syntax

advanced

Identifying a Syntax Error in a GraphQL Query

Which option contains a syntax error in the GraphQL query?

GraphQL

query {
  user(id: "1") {
    name
    email
  }
}

A

query {
  user(id: "1") {
    name
    email
  }

B

query {
  user(id: 1) {
    name
    email
  }
}

C

query {
  user(id: "1") {
    name
    email
  }
}

D

query {
  user(id: "1") {
    name
    email
  }
  extraField
}

💡 Hint

Look for missing or extra braces.

Option A is missing the closing brace for the query, causing a syntax error.

❓ optimization

advanced

Best Practice to Prevent Introspection Abuse

Which method best helps prevent attackers from abusing GraphQL introspection in production?

A Allow introspection only for authenticated users

B Cache introspection results to speed up queries

C Disable introspection queries in production environments

D Increase query complexity limits

💡 Hint

Think about hiding schema details from attackers.

Disabling introspection in production hides schema details, making it harder for attackers to learn about the API structure.

🔧 Debug

expert

Debugging a Rate Limiting Issue

A GraphQL API implements rate limiting per IP address but some users report they can send unlimited queries. What is the most likely cause?

A Users are behind a shared proxy, so rate limiting applies to the proxy IP, not individual users

B The rate limiting middleware is applied after the query execution

C The API uses query complexity analysis instead of IP-based limits

D The server has no network firewall enabled

💡 Hint

Consider how IP addresses are seen by the server.

If many users share the same IP (like behind a proxy), rate limiting per IP affects all users together, allowing individuals to bypass limits.

Practice

1. What is the main purpose of authentication in GraphQL security?

easy

A. To encrypt the data sent between client and server

B. To limit the number of queries a user can make

C. To verify the identity of the user making the request

D. To format the GraphQL schema correctly

Solution

1. Step 1: Understand authentication role

   Authentication checks who the user is before allowing access.

2. Step 2: Differentiate from other security measures

   Limiting queries and encryption are different security aspects, not authentication.

3. Final Answer:

   To verify the identity of the user making the request -> Option C

4. Quick Check:

   Authentication = Verify user identity [OK]

Hint: Authentication means checking who you are [OK]

Common Mistakes:

• Confusing authentication with authorization
• Thinking authentication limits query size
• Mixing authentication with encryption

2. Which of the following is the correct way to limit query complexity in a GraphQL server?

easy

A. Allow unlimited queries and rely on client honesty

B. Use SQL injection to filter queries

C. Disable authentication to speed up queries

D. Use a middleware that calculates query depth and rejects too deep queries

Solution

1. Step 1: Identify query complexity control

   Middleware can analyze query depth and reject overly complex queries to protect the server.

2. Step 2: Eliminate incorrect options

   Allowing unlimited queries or disabling authentication weakens security; SQL injection is an attack, not a defense.

3. Final Answer:

   Use a middleware that calculates query depth and rejects too deep queries -> Option D

4. Quick Check:

   Limit query complexity = Middleware checks depth [OK]

Hint: Middleware can block too complex queries [OK]

Common Mistakes:

• Ignoring query complexity limits
• Confusing SQL injection with security measure
• Disabling authentication to improve speed

3. Given this GraphQL resolver snippet, what will happen if a user without proper role tries to access the data?

const resolver = (parent, args, context) => {
  if (!context.user.roles.includes('admin')) {
    throw new Error('Access denied');
  }
  return getData();
};

medium

A. An error 'Access denied' will be thrown for non-admin users

B. The data will be returned regardless of user role

C. The server will crash due to missing roles

D. The resolver will ignore the role check and return null

Solution

1. Step 1: Analyze role check in resolver

   The code checks if the user roles include 'admin'. If not, it throws an error.

2. Step 2: Understand error handling

   Throwing an error stops execution and returns 'Access denied' to the client.

3. Final Answer:

   An error 'Access denied' will be thrown for non-admin users -> Option A

4. Quick Check:

   Role check fails = Error thrown [OK]

Hint: Throw error if user lacks role [OK]

Common Mistakes:

• Assuming data returns without role check
• Thinking server crashes on missing role
• Believing null is returned instead of error

4. Identify the security issue in this GraphQL server setup:

const server = new ApolloServer({
  typeDefs,
  resolvers,
  context: ({ req }) => ({ user: req.user })
});

// No rate limiting or query complexity checks applied

medium

A. Missing authentication in context setup

B. No rate limiting or query complexity protection

C. Resolvers are not defined

D. Using ApolloServer is insecure

Solution

1. Step 1: Review context and security features

   Context passes user info, so authentication may exist, but no rate limiting or complexity checks are shown.

2. Step 2: Identify missing protections

   Without rate limiting and query complexity checks, server is vulnerable to overload and abuse.

3. Final Answer:

   No rate limiting or query complexity protection -> Option B

4. Quick Check:

   Missing limits = Vulnerable server [OK]

Hint: Always add rate limits and complexity checks [OK]

Common Mistakes:

• Assuming ApolloServer is insecure by default
• Confusing missing resolvers with security issue
• Ignoring rate limiting importance

5. You want to protect your GraphQL API from abuse by limiting both query complexity and request rate. Which combination of methods is best practice?

hard

A. Implement query depth analysis middleware and use a rate limiter like Redis to track requests

B. Only use authentication tokens without any query or rate limits

C. Disable introspection to prevent all queries

D. Allow unlimited queries but log all requests for later review

Solution

1. Step 1: Understand query complexity protection

   Middleware that analyzes query depth helps prevent expensive queries that overload the server.

2. Step 2: Understand rate limiting

   Using a rate limiter like Redis tracks and limits how many requests a user can make in a time window.

3. Step 3: Evaluate other options

   Authentication alone doesn't limit abuse; disabling introspection breaks development; logging alone doesn't prevent abuse.

4. Final Answer:

   Implement query depth analysis middleware and use a rate limiter like Redis to track requests -> Option A

5. Quick Check:

   Combine depth check + rate limiter = Best protection [OK]

Hint: Use middleware plus rate limiter for best security [OK]

Common Mistakes:

• Relying only on authentication
• Disabling introspection breaks tools
• Logging without limiting requests