cve.bz

CVE-2022-21708 graphql-go project graphql-go: Uncontrolled Recursion

6.5 mediumEPSS 1.3%Fix available

Medium (6.5) in graphql-go project graphql-go. EPSS 1.3% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/graph-gophers/graphql-go 1.3.0.

On this page
graphql-go is a GraphQL server with a focus on ease of use. In versions prior to 1.3.0 there exists a DoS vulnerability that is possible due to a bug in the library that would allow an attacker with specifically designed queries to cause stack overflow panics. Any user with access to the GraphQL handler can send these queries and cause stack overflows. This in turn could potentially compromise the ability of the server to serve data to its users. The issue has been patched in version `v1.3.0`. The only known workaround for this issue is to disable the `graphql.MaxDepth` option from your schema which is not recommended.

Severity

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
1.3% (unchanged from 1.3% a week ago; 1.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 72nd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2025-04-23. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-674 Uncontrolled Recursion
CWE-400 Uncontrolled Resource Consumption
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2022-21708 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-21708?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-21708?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2022-21708 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
graphql-go_project:graphql-gobefore 1.3.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-mh3m-8c74-74xhGogithub.com/graph-gophers/graphql-go<1.3.01.3.0
GO-2022-0300Gogithub.com/graph-gophers/graphql-go<1.3.01.3.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14golang-github-graph-gophers-graphql-go1.3.0-1DEBIAN-CVE-2022-21708
Ubuntu20.04:LTSgolang-github-graph-gophers-graphql-gono fix listedUBUNTU-CVE-2022-21708

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Moderate.

ProductPackageStateAdvisory
Red Hat OpenShift Container Platform 4.12openshift4/ose-console:v4.12.0-202406190905.p0.g8654e63.assembly.stream.el8Fixed 2024-06-27RHSA-2024:4006
Red Hat OpenShift Container Platform 4.13openshift4/ose-console:v4.13.0-202406112237.p0.gdc7be0c.assembly.stream.el8Fixed 2024-06-19RHSA-2024:3885
Red Hat OpenShift Container Platform 4.14openshift4/ose-console:v4.14.0-202402061340.p0.g3cab6c4.assembly.stream.el8Fixed 2024-02-13RHSA-2024:0735
Red Hat Advanced Cluster Security 3graphql-goAffected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2022-21708.

Attack patterns (CAPEC)

  • CAPEC-230 Serialized Data with Nested Payloads Likelihood: Medium · Severity: High
  • CAPEC-231 Oversized Serialized Data Payloads Likelihood: Medium · Severity: High
  • CAPEC-147 XML Ping of the Death Likelihood: Low · Severity: Medium
  • CAPEC-227 Sustained Client Engagement
  • CAPEC-492 Regular Expression Exponential Blowup

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON