CVE-2024-43783: Apollo router Apollo Router Coprocessors May Cause Vulnerability

HIGH
Advisory Identifier: GHSA-x6xq-whh3-gg32
CVSS 7.5
CWE-770
Published
Advisory Summary

CVE-2024-43783 is a HIGH (CVSS 7.5) apollo router coprocessors may cause vulnerability (CWE-770: Allocation of Resources Without Limits or Throttling) affecting Apollo router libraries in the crates.io ecosystem. The issue involves apollo router coprocessors may cause denial-of-service when handling request bodies. Remediation is available by upgrading affected packages to version 1.52.1.

CVE-2024-43783 at a Glance

CVE Identifier CVE-2024-43783
GHSA Identifier GHSA-x6xq-whh3-gg32
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification CWE-770: Allocation of Resources Without Limits or Throttling
Affected Product Apollo router
Package Ecosystem crates.io
Published Date
Last Updated

Security Impact

CVSS: 7.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability High (A:H)

How to Fix CVE-2024-43783

To remediate this vulnerability, upgrade all affected Apollo router dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

apollo-router fixed: 1.52.1
Upgrade apollo-router to 1.52.1
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for apollo-router

How to Check if You Are Affected

To determine whether your application is affected by CVE-2024-43783, inspect your project dependencies for Apollo router:

inspect dependencies for apollo-router

Analyze the terminal output to locate any version of Apollo router in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.52.1), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-770: Allocation of Resources Without Limits or Throttling, where the product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated. In Apollo router, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## 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.52.1 are impacted by a denial-of-service vulnerability if **all** of the following are true: 1. Router has been configured to support External Coprocessing. 2. Router has been configured to send request bodies to coprocessors. This is a non-default configuration and must be configured intentionally by administrators. You can identify if you are impacted by reviewing your router's configuration YAML for the following config: ```yaml ... coprocessor: url: http://localhost:9000 # likely different in your environment router: request: body: true # this must be set to 'true' to be impacted ... ``` External Coprocessing was initially made available as an experimental feature with [Router version 1.21.0](https://github.com/apollographql/router/releases/tag/v1.21.0) on 2023-06-20 and was made generally available with [Router version 1.38.0](https://github.com/apollographql/router/releases/tag/v1.38.0) on 2024-01-19. More information about the Router’s [External Coprocessing feature is available here](https://www.apollographql.com/docs/router/customizations/coprocessor). ### When using Native Rust Plugins: Instances of the Apollo Router running versions >=1.7.0 and <1.52.1 are impacted by a denial-of-service vulnerability if **all** of the following are true: 1. Router has been configured to use a custom-developed Native Rust Plugin 2. The plugin accesses `Request.router_request` in the `RouterService` layer 3. You are accumulating the body from `Request.router_request` into memory To use a plugin, you need to be running a customized Router binary. Additionally, you need to have a `plugins` section with at least one plugin defined in your Router’s configuration YAML. That plugin would also need to define a custom `router_service` method. You can check for a defined plugin by reviewing for the following in your Router’s configuration YAML: ```yaml ... plugins: custom_plugin_name: # custom config here ... ``` You can check for a custom `router_service` method in a plugin, by reviewing for the following function signature in your plugin’s source: ```rust fn router_service(&self, service: router::BoxService) -> router::BoxService ``` More information about the Router’s [Native Rust Plugin feature is available here](https://www.apollographql.com/docs/router/customizations/native). ## 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](https://www.apollographql.com/docs/router/configuration/overview/#request-limits). ## Patches [Apollo Router 1.52.1](https://github.com/apollographql/router/releases/tag/v1.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](https://github.com/apollographql/router/releases/tag/v1.52.1) [External Coprocessing documentation](https://www.apollographql.com/docs/router/customizations/coprocessor) [HTTP Request Limiting documentation](https://www.apollographql.com/docs/router/configuration/overview/#request-limits) [Native Rust Plugin documentation](https://www.apollographql.com/docs/router/customizations/native)

CVE-2024-43783 Affected Apollo router Versions

1 component(s)
Fixed Versions:
1.52.1
Product / Package Ecosystem Affected Versions Fixed Version
apollo-router
crates.io
≥ 1.7.0
< 1.52.1
1.52.1

References

Frequently Asked Questions

What is CVE-2024-43783?
CVE-2024-43783 is a security vulnerability in Apollo router involving Apollo Router Coprocessors may cause Denial-of-Service when handling request bodies under CWE-770: Allocation of Resources Without Limits or Throttling.
Which Apollo router versions are affected?
Affected versions include releases prior to 1.52.1 across affected packages: apollo-router.
What version fixes CVE-2024-43783?
Upgrading to 1.52.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is apollo-router affected?
Yes, apollo-router is affected in releases prior to 1.52.1. Upgrade your dependency to 1.52.1 or later.
What is the CVSS score of CVE-2024-43783?
CVE-2024-43783 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2024-43783?
CVE-2024-43783 is classified under CWE-770: Allocation of Resources Without Limits or Throttling (The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.).
How can I check crates.io dependencies for CVE-2024-43783?
Run the dependency tree command: 'inspect dependencies for apollo-router'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-x6xq-whh3-gg32",
  "modified" : "2024-08-27T20:31:40Z",
  "published" : "2024-08-27T18:14:29Z",
  "aliases" : [ "CVE-2024-43783" ],
  "summary" : "Apollo Router Coprocessors may cause Denial-of-Service when handling request bodies",
  "details" : "## Impact\n\nInstances of the Apollo Router using either of the following may be impacted by a denial-of-service vulnerability.\n\n1. External Coprocessing with specific configurations; or\n2. Native Rust Plugins accessing the Router request body in the RouterService layer \n\nRouter customizations using Rhai scripts are **not** impacted.\n\n### When using External Coprocessing:\n\nInstances of the Apollo Router running versions >=1.21.0 and <1.52.1 are impacted by a denial-of-service vulnerability if **all** of the following are true:\n\n1. Router has been configured to support External Coprocessing.\n2. Router has been configured to send request bodies to coprocessors. This is a non-default configuration and must be configured intentionally by administrators.\n\nYou can identify if you are impacted by reviewing your router's configuration YAML for the following config:\n\n```yaml\n...\ncoprocessor:\n  url: http://localhost:9000 # likely different in your environment\n  router:\n    request:\n      body: true # this must be set to 'true' to be impacted\n...\n```\nExternal Coprocessing was initially made available as an experimental feature with [Router version 1.21.0](https://github.com/apollographql/router/releases/tag/v1.21.0) on 2023-06-20 and was made generally available with [Router version 1.38.0](https://github.com/apollographql/router/releases/tag/v1.38.0) on 2024-01-19. More information about the Router’s [External Coprocessing feature is available here](https://www.apollographql.com/docs/router/customizations/coprocessor).\n\n### When using Native Rust Plugins:\n\nInstances of the Apollo Router running versions >=1.7.0 and <1.52.1 are impacted by a denial-of-service vulnerability if **all** of the following are true:\n\n1. Router has been configured to use a custom-developed Native Rust Plugin\n2. The plugin accesses `Request.router_request` in the `RouterService` layer\n3. You are accumulating the body from `Request.router_request` into memory\n\nTo use a plugin, you need to be running a customized Router binary. Additionally, you need to have a `plugins` section with at least one plugin defined in your Router’s configuration YAML. That plugin would also need to define a custom `router_service` method.\n\nYou can check for a defined plugin by reviewing for the following in your Router’s configuration YAML:\n\n```yaml\n...\nplugins:\n    custom_plugin_name:\n        # custom config here\n...\n```\n\nYou can check for a custom `router_service` method in a plugin, by reviewing for the following function signature in your plugin’s source:\n\n```rust\nfn router_service(&self, service: router::BoxService) -> router::BoxService\n```\n\nMore information about the Router’s [Native Rust Plugin feature is available here](https://www.apollographql.com/docs/router/customizations/native).\n\n## Impact Detail\n\nIf 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.\n\nBy default, the Router sets `limits.http_max_request_bytes` to 2 MB. More information about the Router’s [request limiting features is available here](https://www.apollographql.com/docs/router/configuration/overview/#request-limits).\n\n## Patches\n\n[Apollo Router 1.52.1](https://github.com/apollographql/router/releases/tag/v1.52.1)\n\nIf you have an impacted configuration as defined above, please upgrade to at least Apollo Router 1.52.1.\n\n## Workarounds\nIf 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. \n\nIf 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. \n\nYou 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).\n\n## References\n[Apollo Router 1.52.1 Release Notes](https://github.com/apollographql/router/releases/tag/v1.52.1)\n[External Coprocessing documentation](https://www.apollographql.com/docs/router/customizations/coprocessor)\n[HTTP Request Limiting documentation](https://www.apollographql.com/docs/router/configuration/overview/#request-limits)\n[Native Rust Plugin documentation](https://www.apollographql.com/docs/router/customizations/native)\n",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
  }, {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "apollo-router"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.7.0"
      }, {
        "fixed" : "1.52.1"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/apollographql/router/security/advisories/GHSA-x6xq-whh3-gg32"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2024-43783"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/apollographql/router/commit/7a9c020608a62dcaa306b72ed0f6980f15923b14"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/apollographql/router"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/apollographql/router/releases/tag/v1.52.1"
  }, {
    "type" : "WEB",
    "url" : "https://www.apollographql.com/docs/router/configuration/overview/#request-limits"
  }, {
    "type" : "WEB",
    "url" : "https://www.apollographql.com/docs/router/customizations/coprocessor"
  }, {
    "type" : "WEB",
    "url" : "https://www.apollographql.com/docs/router/customizations/native"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-770" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-08-27T18:14:29Z",
    "nvd_published_at" : "2024-08-27T18:15:15Z"
  }
}