GHSA-5xh2-23cc-5jc6
Suggest an improvement- Source
- https://github.com/advisories/GHSA-5xh2-23cc-5jc6
- Import Source
- https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2025/01/GHSA-5xh2-23cc-5jc6/GHSA-5xh2-23cc-5jc6.json
- JSON Data
- https://api.osv.dev/v1/vulns/GHSA-5xh2-23cc-5jc6
- Aliases
- Published
- 2025-01-09T18:51:51Z
- Modified
- 2025-01-09T22:24:40.183267Z
- Severity
-
- 3.7 (Low) CVSS_V3 - CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N CVSS Calculator
- Summary
- Strawberry GraphQL has type resolution vulnerability in node interface that allows potential data leakage through incorrect type resolution
- Details
-
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
nodeinterface.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.Node2. These types are mapped to the same database model 3. The globalnodefield is used for type resolutionExample 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
nodefield (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 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.05. If usingstrawberry-graphql-django, update tostrawberry-graphql-django>=0.54.0 - Database specific
{ "nvd_published_at": "2025-01-09T19:15:20Z", "severity": "LOW", "github_reviewed_at": "2025-01-09T18:51:51Z", "github_reviewed": true, "cwe_ids": [ "CWE-351", "CWE-843" ] }- References
Affected packages
PyPI / strawberry-graphql
Package
- Name
- strawberry-graphql
- View open source insights on deps.dev
- Purl
- pkg:pypi/strawberry-graphql