GitHub Advisoryadvisory · crates.io
GHSA-x6xq-whh3-gg32 Apollo Router Coprocessors may cause Denial-of-Service when handling request bodies
HIGH
Official page ↗
- Aliases
- CVE-2024-43783
- Ecosystem
- crates.io
- Packages
- apollo-router
- Severity
- High
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Weaknesses
- CWE-770
- Reviewed
- 2024-08-27
Affected packages
• crates.io apollo-router: >= 1.7.0, < 1.52.1 → fixed in 1.52.1
Description
Impact
Instances of the Apollo Router using either of the following may be impacted by a denial-of-service vulnerability.
1. External Coprocessing with specific configurations; or
2. Native Rust Plugins accessing the Router request body in the RouterService layer
Router customizations using Rhai scripts are not impacted.
When using External Coprocessing:
Instances of the Apollo Router running versions >=1.21.0 and =1.7.0 and router::BoxService
```
More information about the Router’s Native Rust Plugin feature is available here.
Impact Detail
If using an impacted configuration, the Router will load entire HTTP request bodies into memory without respect to other HTTP request size-limiting configurations like `limits.http_max_request_bytes`. This can cause the Router to be out-of-memory (OOM) terminated if a sufficiently large request is sent to the Router.
By default, the Router sets `limits.http_max_request_bytes` to 2 MB. More information about the Router’s request limiting features is available here.
Patches
Apollo Router 1.52.1
If you have an impacted configuration as defined above, please upgrade to at least Apollo Router 1.52.1.
Workarounds
If you cannot upgrade, you can mitigate the denial-of-service opportunity impacting External Coprocessors by setting the `coprocessor.router.request.body` configuration option to `false`. Please note that changing this configuration option will change the information sent to any coprocessors you have configured and may impact functionality implemented by those coprocessors.
If you have developed a Native Rust Plugin and cannot upgrade, you can update your plugin to either not accumulate the request body or enforce a maximum body size limit.
You can also mitigate this issue by limiting HTTP body payload sizes prior to the Router (e.g., in a proxy or web application firewall appliance).
References
Apollo Router 1.52.1 Release Notes
External Coprocessing documentation
HTTP Request Limiting documentation
Native Rust Plugin documentation
Related
Alias · CVE (1)
- CVE-2024-43783 The Apollo Router Core is a configurable, high-performance graph router written in Rust to run a federated supergraph that uses Apollo… vulnerability
Weakness · CWE (1)
- CWE-770 Allocation of Resources Without Limits or Throttling weakness
References
- https://github.com/apollographql/router/security/advisories/GHSA-x6xq-whh3-gg32 web
- https://nvd.nist.gov/vuln/detail/CVE-2024-43783 advisory
- https://github.com/apollographql/router/commit/7a9c020608a62dcaa306b72ed0f6980f15923b14 web
- https://github.com/apollographql/router package
- https://github.com/apollographql/router/releases/tag/v1.52.1 web
- https://www.apollographql.com/docs/router/configuration/overview/#request-limits web
- https://www.apollographql.com/docs/router/customizations/coprocessor web
- https://www.apollographql.com/docs/router/customizations/native web