Headline

GHSA-5xh2-23cc-5jc6: Strawberry GraphQL has type resolution vulnerability in node interface that allows potential data leakage through incorrect type resolution

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:

Multiple GraphQL types inherit from relay.Node
These types are mapped to the same database model
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:

Information disclosure if the alternate type exposes sensitive fields
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

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

9 hours ago

ghsa

Open in Source

#sql #vulnerability #auth

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:

Multiple GraphQL types inherit from relay.Node
These types are mapped to the same database model
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:

Information disclosure if the alternate type exposes sensitive fields
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

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

References