Skip to content

async-graphql / async-graphql - @DOS GraphQL Nested Fragments overflow

High severity GitHub Reviewed Published Jul 26, 2022 in async-graphql/async-graphql • Updated Jan 6, 2023

Package

cargo async-graphql (Rust)

Affected versions

< 4.0.6

Patched versions

4.0.6

Description

Impact

Executing deeply nested queries may cause stack overflow.

Patches

Upgrade to v4.0.6

References

@sunli829 sunli829 published to async-graphql/async-graphql Jul 26, 2022
Published to the GitHub Advisory Database Jul 29, 2022
Reviewed Jul 29, 2022
Last updated Jan 6, 2023

Severity

High

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
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Weaknesses

No CWEs

CVE ID

No known CVE

GHSA ID

GHSA-xq3c-8gqm-v648

Source code

Credits

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