Security readout for executives and security teams
Plain-English summary
Hasura GraphQL 1.3.3 may let an unauthenticated remote attacker turn a database query into operating-system command execution. Successful exploitation could expose data, alter systems, or interrupt services. Risk is greatest where the affected administrative SQL capability is reachable from untrusted networks.
Executive priority
Treat confirmed 1.3.3 deployments as an immediate remediation priority because compromise could provide full command execution without user interaction. Rapidly inventory exposure, restrict access, investigate suspicious activity, and obtain vendor-confirmed upgrade guidance. Public exploit material exists, but active exploitation is not established by the supplied evidence.
Technical view
The flaw is command injection through the run_sql endpoint. A crafted GraphQL request can manipulate SQL into invoking PostgreSQL COPY FROM PROGRAM, resulting in arbitrary shell-command execution. The supplied CVSS 3.1 score is 9.8, reflecting network access, low complexity, no required privileges or user interaction, and high impact.
Likely exposure
Confirmed scope in the supplied sources is limited to Hasura GraphQL 1.3.3. Prioritize instances where run_sql or related administrative APIs are reachable externally or without effective authentication. The bundle does not establish that other versions are affected.
Exploitation context
A public ExploitDB entry exists, demonstrating public exploit knowledge. However, this CVE is not listed as KEV in the supplied bundle, and no cited evidence establishes active exploitation in the wild. Public availability increases practical risk without proving current attacks.
Researcher notes
The claimed chain crosses GraphQL handling, SQL execution, and PostgreSQL operating-system program execution. Validate endpoint reachability, authentication controls, database privileges, and host evidence without reproducing the public exploit against production. The sources do not identify a patched version or vendor advisory, so remediation-version certainty is incomplete.
Mitigation direction
- Inventory and isolate Hasura GraphQL 1.3.3 deployments, prioritizing internet-reachable instances.
- Restrict run_sql and administrative interfaces to trusted, authenticated operators.
- Check current Hasura guidance and upgrade only to a vendor-confirmed non-affected release.
- Treat PostgreSQL program-execution privileges as sensitive and reduce them where operationally safe.
- Monitor Hasura, PostgreSQL, and host telemetry for suspicious command-execution activity.
Validation and detection
- Confirm the Hasura version running in every environment and container image.
- Determine whether untrusted or unauthenticated clients can reach run_sql.
- Review logs for unexpected run_sql requests or COPY FROM PROGRAM activity.
- Inspect affected hosts for unexplained child processes, persistence, or configuration changes.
- After remediation, verify administrative interfaces remain inaccessible to untrusted clients.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-78: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. 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 lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2021-47748 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
SSVC decision data
CVSS vector scores
2 official scoresWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9VulnCheckCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
9.3CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- ExploitDB-49802CVE reference, VulnCheck · exploit
- Hasura GraphQL Engine GitHub RepositoryCVE reference, VulnCheck · product
- VulnCheck Advisory: Hasura GraphQL 1.3.3 - Remote Code ExecutionCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.