Open-Source Security Intelligence

Know every vulnerability
before it knows you.

DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.

Search

GHSA-5xh2-23cc-5jc6

LowCVSS 3.7 / 10
Published Jan 9, 2025·Last modified Jan 9, 2025
Affected Components(0)

No affected components available

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
Risk Scores
Base Score
3.7

The vulnerability can be exploited over the network without needing physical access. It is difficult for an attacker to exploit this vulnerability and may require special conditions. An attacker does not need any special privileges or access rights. No user interaction is needed for the attacker to exploit this vulnerability. The impact is confined to the system where the vulnerability exists. There is a low impact on the confidentiality of the information.

Threat Intelligence
3.4

Limited exploitation activity has been observed. Close monitoring and planned remediation are recommended.

EPSS
0.37%

The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.

Exploit
Not available

We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.

Browse More

Scan your project

Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.

Checkout DevGuard