Service disruption via unlimited field directives
Published Oct 3, 2024 · Updated Oct 3, 2024
Resource exhaustion in async-graphql before 7.0.10 allows remote attackers to interrupt service using fields with many directives. Request preparation traverses field selections without bounding directive counts, so validation processes every supplied directive. An unauthenticated, network-reachable GraphQL endpoint that accepts attacker-controlled queries exposes CPU and memory exhaustion, causing severe slowdown or unresponsiveness.
Summary
What happened
Resource exhaustion in async-graphql before 7.0.10 allows remote attackers to interrupt service using fields with many directives. Request preparation traverses field selections without bounding directive counts, so validation processes every supplied directive. An unauthenticated, network-reachable GraphQL endpoint that accepts attacker-controlled queries exposes CPU and memory exhaustion, causing severe slowdown or unresponsiveness.
The record
- CVE
- CVE-2024-47614
- Published
- Oct 3, 2024
- Updated
- Oct 3, 2024
- Vendor
- async-graphql
- Product
- async-graphql
- Classifications
- CWE-770, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 3, 2024CVE publishedPublication date reported by the CVE source.
- Oct 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <7.0.10
- Affected versionversion=< 7.0.10
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo