Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| graphql-go project | graphql-go | unknown |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Graphql-go Project | Graphql-go |
|
Vendor Workaround
Decode GraphQL variables with a deserializer that enforces a maximum nesting depth (Go's standard encoding/json does), which mitigates the stack-overflow condition. There is no library-level workaround for the type-confusion condition short of application-side validation of scalar arguments or a custom scalar; upgrading once a fix ships is the durable remedy.
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.184% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | github.com/graphql-go/graphql (GraphQL for Go) through 0.8.1 does not validate that a scalar variable value matches its declared type. The built-in coerceString and coerceBool functions (scalars.go) accept input whose type does not match the declared String, ID, or Boolean scalar instead of raising the request error that the GraphQL specification mandates. In some cases (but not any typical case of JSON sent to a website), a deeply nested value leads to an unrecoverable "fatal error: stack overflow" condition. | |
| First Time appeared |
Graphql-go Project
Graphql-go Project graphql-go |
|
| Weaknesses | CWE-1287 | |
| CPEs | cpe:2.3:a:graphql-go_project:graphql-go:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Graphql-go Project
Graphql-go Project graphql-go |
|
| References |
| |
| Metrics |
cvssV4_0
|