Vulnerabilities in pkg:golang/github.com/graph-gophers/graphql-go

PACKAGE
Advisory Identifier: GHSA-mh3m-8c74-74xh
Share
Advisory Summary

CVE-2022-21708 is a MODERATE (CVSS 6.5) denial of service vulnerability (CWE-400: Uncontrolled Resource Consumption) affecting Github.com/graph gophers/graphql go libraries in the Go ecosystem. The issue involves denial of service in graphql-go. Remediation is available by upgrading affected packages to version 1.3.0.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:golang/github.com/graph-gophers/graphql-go

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:golang/github.com/graph-gophers/graphql-go. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-mh3m-8c74-74xh CVE-2022-21708 MODERATE Denial of Service in graphql-go

CVE-2022-21708 at a Glance

CVE Identifier CVE-2022-21708
GHSA Identifier GHSA-mh3m-8c74-74xh
Severity MODERATE
CVSS v3.1 Base Score 6.5
CWE Classification CWE-400: Uncontrolled Resource Consumption
Affected Product Github.com/graph gophers/graphql go
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 6.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability High (A:H)

How to Fix CVE-2022-21708

To remediate this vulnerability, upgrade all affected Github.com/graph gophers/graphql go dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/graph-gophers/graphql-go fixed: 1.3.0 
Upgrade github.com/graph-gophers/graphql-go to 1.3.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

inspect dependencies for github.com/graph-gophers/graphql-go

How to Check if You Are Affected

To determine whether your application is affected by CVE-2022-21708, inspect your project dependencies for Github.com/graph gophers/graphql go:

inspect dependencies for github.com/graph-gophers/graphql-go

Analyze the terminal output to locate any version of Github.com/graph gophers/graphql go in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.3.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-400: Uncontrolled Resource Consumption, where the product does not properly control the allocation and maintenance of a limited resource. In Github.com/graph gophers/graphql go, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact This is 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. To make things worse the only mitigation in affected versions creates opportunities for other attacks. This issue is only available if you are using `graphql.MaxDepth` option in your schema (which is highly recommended in most cases). ### Patches The issue has been patched in version `v1.3.0`. We have been trying to maintain backwards compatibility and avoid breaking changes so upgrading should not be problematic. ### Workarounds The best workaround is to patch to a version greater than or equal to `v1.3.0`. Otherwise, the only workaround in versions prior to `v1.3.0` is to disable the `graphql.MaxDepth` option from your schema. Unfortunately, this could potentially create opportunities for other attacks. ### References There are no references or links. This issue was reported privately and was fixed before creating this Security Advisory. ### For more information If you have any questions or comments feel free to reach out to @pavelnikolov or @tony on the Gopher Slack.

CVE-2022-21708 Affected Github.com/graph gophers/graphql go Versions

1 component(s)
Fixed Versions:
1.3.0
Product / Package Ecosystem Affected Versions Fixed Version
github.com/graph-gophers/graphql-go
golang/github.com/graph-gophers/graphql-go
Go
< 1.3.0
1.3.0

References

GitHub Advisory / Wiki ADVISORY
https://github.com/graph-gophers/graphql-go/security/advisories/GHSA-mh3m-8c74-74xh
NVD — CVE-2022-21708 NVD
https://nvd.nist.gov/vuln/detail/CVE-2022-21708
Security Fix Commit FIX COMMIT
https://github.com/graph-gophers/graphql-go/commit/eae31ca73eb3473c544710955d1dbebc22605bfe
Github.com/graph gophers/graphql go Source Repository REPOSITORY
https://github.com/graph-gophers/graphql-go
pkg.go.dev/vuln/go-2022-0300 WEB
https://pkg.go.dev/vuln/GO-2022-0300

Frequently Asked Questions

What is CVE-2022-21708?
CVE-2022-21708 is a security vulnerability in Github.com/graph gophers/graphql go involving Denial of Service in graphql-go under CWE-400: Uncontrolled Resource Consumption.
Which Github.com/graph gophers/graphql go versions are affected?
Affected versions include releases prior to 1.3.0 across affected packages: github.com/graph-gophers/graphql-go.
What version fixes CVE-2022-21708?
Upgrading to 1.3.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/graph-gophers/graphql-go affected?
Yes, github.com/graph-gophers/graphql-go is affected in releases prior to 1.3.0. Upgrade your dependency to 1.3.0 or later.
What is the CVSS score of CVE-2022-21708?
CVE-2022-21708 has a CVSS v3.1 base score of 6.5 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2022-21708?
CVE-2022-21708 is classified under CWE-400: Uncontrolled Resource Consumption (The product does not properly control the allocation and maintenance of a limited resource.).
How can I check Go dependencies for CVE-2022-21708?
Run the dependency tree command: 'inspect dependencies for github.com/graph-gophers/graphql-go'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-mh3m-8c74-74xh",
  "modified" : "2022-01-31T21:59:33Z",
  "published" : "2022-01-27T15:28:06Z",
  "aliases" : [ "CVE-2022-21708" ],
  "summary" : "Denial of Service in graphql-go",
  "details" : "### Impact\nThis is 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. To make things worse the only mitigation in affected versions creates opportunities for other attacks. This issue is only available if you are using `graphql.MaxDepth` option in your schema (which is highly recommended in most cases).\n\n### Patches\nThe issue has been patched in version `v1.3.0`. We have been trying to maintain backwards compatibility and avoid breaking changes so upgrading should not be problematic. \n\n### Workarounds\nThe best workaround is to patch to a version greater than or equal to `v1.3.0`. \nOtherwise, the only workaround in versions prior to `v1.3.0` is to disable the `graphql.MaxDepth` option from your schema. Unfortunately, this could potentially create opportunities for other attacks.\n\n### References\nThere are no references or links. This issue was reported privately and was fixed before creating this Security Advisory.\n\n### For more information\nIf you have any questions or comments feel free to reach out to @pavelnikolov or @tony on the Gopher Slack.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/graph-gophers/graphql-go"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.3.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/graph-gophers/graphql-go/security/advisories/GHSA-mh3m-8c74-74xh"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2022-21708"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/graph-gophers/graphql-go/commit/eae31ca73eb3473c544710955d1dbebc22605bfe"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/graph-gophers/graphql-go"
  }, {
    "type" : "WEB",
    "url" : "https://pkg.go.dev/vuln/GO-2022-0300"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-400" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2022-01-24T22:42:15Z",
    "nvd_published_at" : "2022-01-21T23:15:00Z"
  }
}