Homepage

graphql-core@3.3.0a6

GraphQL-core is a Python port of GraphQL.js, the JavaScript reference implementation for GraphQL.

  • latest version

    3.3.0

  • latest non vulnerable version

    3.3.0

  • first published

    11 years ago

  • latest version published

    26 days ago

  • licenses detected

  • View graphql-core package health on Snyk  (opens in a new tab)
    • Go back to all versions of this package
    Report a new vulnerability Found a mistake?

    Direct Vulnerabilities

    Known vulnerabilities in the graphql-core package. This does not include vulnerabilities belonging to this package’s dependencies.

    Fix vulnerabilities automatically

    Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

    Fix for free
    VulnerabilityVulnerable Version
    • H
    Allocation of Resources Without Limits or Throttling

    graphql-core is a GraphQL implementation for Python, a port of GraphQL.js, the JavaScript reference implementation for GraphQL.

    Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling via the advance_lexer function in src/graphql/language/parser.py, where comment tokens are allocated as Token objects and chained into the token linked-list but were not counted toward the max_tokens limit. An attacker can submit a comment-padded GraphQL document that bypasses the max_tokens guard, causing unbounded memory allocation - one Token object per comment - until memory is exhausted.

    How to fix Allocation of Resources Without Limits or Throttling?

    Upgrade graphql-core to version 3.2.12, 3.3.0rc1 or higher.

    [3.2.3,3.2.12)[3.3.0a3,3.3.0rc1)
    • H
    Inefficient Algorithmic Complexity

    graphql-core is a GraphQL implementation for Python, a port of GraphQL.js, the JavaScript reference implementation for GraphQL.

    Affected versions of this package are vulnerable to Inefficient Algorithmic Complexity via the OverlappingFieldsCanBeMergedRule validation rule in overlapping_fields_can_be_merged.py. The rule compares every pair of fields sharing a response name and recurses into their sub-selections, producing O(n^2) complexity that worsens when inline fragments repeat the same response name at multiple nesting levels. An attacker can send a query that drives validation into minutes of CPU consumption on a single request, exhausting server resources.

    How to fix Inefficient Algorithmic Complexity?

    Upgrade graphql-core to version 3.2.12, 3.3.0rc1 or higher.

    [3.0.0,3.2.12)[3.3.0a1,3.3.0rc1)
    Go back to all versions of this package