Denial of service via undefined error context
Published Dec 13, 2021 · Updated Aug 4, 2024
Denial of service in Mercurius 8.10.0 through 8.11.1 allows remote attackers to crash GraphQL request handling with malformed JSON. The default error handler passes an undefined request context to defaultErrorFormatter, which dereferences reply and throws an uncaught TypeError. Unauthenticated access to /graphql is sufficient; deployments with a custom error handler do not expose this path.
Summary
What happened
Denial of service in Mercurius 8.10.0 through 8.11.1 allows remote attackers to crash GraphQL request handling with malformed JSON. The default error handler passes an undefined request context to defaultErrorFormatter, which dereferences reply and throws an uncaught TypeError. Unauthenticated access to /graphql is sufficient; deployments with a custom error handler do not expose this path.
The record
- CVE
- CVE-2021-43801
- Published
- Dec 13, 2021
- Updated
- Aug 4, 2024
- Vendor
- mercurius-js
- Product
- Mercurius
- Classifications
- CWE-248, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 13, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 8.10.0, < 8.11.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Malformed JSON regression testproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo