Skip to content

Strawberry GraphQL has type resolution vulnerability in node interface that allows potential data leakage through incorrect type resolution

Low severity GitHub Reviewed Published Jan 9, 2025 in strawberry-graphql/strawberry • Updated Jan 9, 2025

Package

pip strawberry-graphql (pip)

Affected versions

>= 0.182.0, < 0.257.0

Patched versions

0.257.0

Description

Vulnerability Summary
A type confusion vulnerability exists in Strawberry GraphQL's relay integration that affects multiple ORM integrations (Django, SQLAlchemy, Pydantic). The vulnerability occurs when multiple GraphQL types are mapped to the same underlying model while using the relay node interface.

Affected Components

  • Strawberry GraphQL relay integration
  • Specifically impacts implementations using:
    • Django integration
    • SQLAlchemy integration
    • Pydantic integration

Technical Details

The vulnerability manifests when:

  1. Multiple GraphQL types inherit from relay.Node
  2. These types are mapped to the same database model
  3. The global node field is used for type resolution

Example of vulnerable code:

from fruits.models import Fruit
import strawberry_django
import strawberry

@strawberry_django.type(Fruit)
class FruitType(relay.Node):
    name: strawberry.auto

@strawberry_django.type(Fruit)
class SpecialFruitType(relay.Node):
    secret_name: strawberry.auto

@strawberry.type
class Query:
    node: relay.Node = strawberry_django.node()

Security Impact

When querying for a specific type using the global node field (e.g., FruitType:some-id), the resolver may incorrectly return an instance of a different type mapped to the same model (e.g., SpecialFruitType). This can lead to:

  1. Information disclosure if the alternate type exposes sensitive fields
  2. Potential privilege escalation if the alternate type contains data intended for restricted access

Note
Even with knowledge of the correct type name (e.g., SpecialFruitType), attackers may still be able to access unauthorized data through direct type queries.

We recommend to use permission on fields instead of creating a dedicate type.

Recommendations

  1. Avoid mapping multiple relay Node types to the same model
  2. Implement strict access controls at the field resolution level (using permissions)
  3. Consider using separate models for different access levels of the same data
  4. Update to strawberry-graphql>=0.257.0
  5. If using strawberry-graphql-django, update to strawberry-graphql-django>=0.54.0

References

Published to the GitHub Advisory Database Jan 9, 2025
Reviewed Jan 9, 2025
Published by the National Vulnerability Database Jan 9, 2025
Last updated Jan 9, 2025

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

CVE ID

CVE-2025-22151

GHSA ID

GHSA-5xh2-23cc-5jc6

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.