Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Low severity, with a CVSS score of 3.1, published 13 June 2019.
- Which products and versions are affected?
- @apollo/gateway (npm) SEMVER:introduced=0,fixed=0.6.2.
- Is there a fix for This vulnerability?
- Yes. @apollo/gateway (npm): upgrade to 0.6.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is This vulnerability attacked?
- It is attacked over the network, in a software library.
- Am I affected?
- Check whether you run @apollo/gateway (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- @apollo/gateway (npm): upgrade to 0.6.2 or later
npm install @apollo/gateway@0.6.2
Technical details
The vulnerability is a prototype pollution flaw in the deepMerge() utility function used by @apollo/gateway. The function failed to filter the __proto__ property when merging objects, allowing attackers to inject payloads through GraphQL aliases that modify Object.prototype. This affects all versions prior to 0.6.2. The attack is network-reachable and requires no authentication. An attacker can manipulate application state to cause denial of service or potentially chain the vulnerability with other issues to achieve remote code execution. The fix, released in version 0.6.2, adds filtering to ignore __proto__ fields during the merge operation.
Affected products
- Apollo @apollo/gateway before 0.6.2
Timeline
- 2019-06-13: disclosed
- 2019-06-04: patched: PR #2779 merged; version 0.6.2 released shortly after