LiveActive security incident?Get immediate response
CVE Record

CVE-2021-47713: Hasura GraphQL 1.3.3 Denial of Service via Malicious GraphQL Query

Hasura GraphQL 1.3.3 contains a denial of service vulnerability that allows attackers to overwhelm the service by crafting malicious GraphQL queries with excessive nested fields. Attackers can send repeated requests with extremely long query strings and multiple threads to consume server resources and potentially crash the GraphQL endpoint.

HighCVSS 8.7Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2021-47713 is a denial-of-service issue in Hasura GraphQL 1.3.3. A remote, unauthenticated attacker could send overly complex nested GraphQL queries to exhaust server resources and make the GraphQL endpoint unavailable. The impact is availability, not data theft or data modification based on the provided sources.

Executive priority

Prioritize remediation for public or business-critical Hasura GraphQL 1.3.3 services. The business risk is service outage and operational disruption. No source-provided evidence indicates data compromise or active exploitation.

Technical view

The vulnerability is categorized as CWE-770: allocation of resources without limits or throttling. The CVSS 4.0 score is 8.7, with network attack vector, low complexity, no privileges, and high vulnerable-system availability impact. The only affected version identified in the source bundle is Hasura GraphQL 1.3.3.

Likely exposure

Exposure is most likely where Hasura GraphQL 1.3.3 is internet-facing or reachable by untrusted clients. Internal deployments may still be exposed if users or services can submit arbitrary GraphQL queries.

Exploitation context

The source bundle includes an Exploit-DB reference, indicating public exploit material exists. The CVE is not listed as KEV, and the provided sources do not state active exploitation in the wild.

Researcher notes

Do not assume other Hasura versions are affected from the provided data. The advisory names version 1.3.3 only. Public exploit reference exists, but active exploitation is not supported by KEV or the provided sources.

Mitigation direction

  • Identify whether Hasura GraphQL 1.3.3 is deployed.
  • Review Hasura vendor guidance and release notes for fixed versions or recommended controls.
  • Restrict untrusted network access to affected GraphQL endpoints where feasible.
  • Apply query complexity, depth, size, and rate controls if supported by your deployment.
  • Monitor endpoint resource usage and availability anomalies.

Validation and detection

  • Inventory Hasura GraphQL versions across production and non-production environments.
  • Confirm whether GraphQL endpoints are exposed to the internet or untrusted networks.
  • Review access logs for unusually long or deeply nested GraphQL queries.
  • Check monitoring for CPU, memory, or service restarts tied to GraphQL traffic.
  • Verify implemented query limits and rate controls are active.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-770: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-47713 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.7 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.7CVSS 4.0HighCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NPrimary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

8.7High
CVSS 4.0 vector shape for CVE-2021-47713Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
HasuraHasura GraphQL1.3.3Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-770 · source CWE mapping

Allocation of Resources Without Limits or Throttling

Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.