[PR #130] [CLOSED] [Security] Bump apollo-server-express from 2.9.14 to 2.14.2 #137

New issue

Closed

opened 2026-02-26 05:30:29 +03:00 by kerem · 0 comments

kerem commented

2026-02-26 05:30:29 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/moollaza/repo-remover/pull/130
Author: @dependabot-preview[bot]
Created: 6/5/2020
Status: ❌ Closed

Base: master ← Head: dependabot/npm_and_yarn/apollo-server-express-2.14.2

📝 Commits (1)

a3427c5 [Security] Bump apollo-server-express from 2.9.14 to 2.14.2

📊 Changes

1 file changed (+497 additions, -297 deletions)

View changed files

📝 yarn.lock (+497 -297)

📄 Description

Bumps apollo-server-express from 2.9.14 to 2.14.2. This update includes a security fix.

Vulnerabilities fixed

Sourced from The GitHub Security Advisory Database.

Introspection in schema validation in Apollo Server We encourage all users of Apollo Server to read this advisory in its entirety to understand the impact. The Resolution section contains details on patched versions.

Impact

If subscriptions: false is passed to the ApolloServer constructor options, there is no impact. If implementors were not expecting validation rules to be enforced on the WebSocket subscriptions transport and are unconcerned about introspection being enabled on the WebSocket subscriptions transport (or were not expecting that), then this advisory is not applicable. If introspection: true is passed to the ApolloServer constructor options, the impact is limited to user-provided validation rules (i.e., using validationRules) since there would be no expectation that introspection was disabled.

The enforcement of user-provided validation rules on the HTTP transport is working as intended and is unaffected by this advisory. Similarly, disabling introspection on the HTTP transport is working as intended and is unaffected by this advisory.

Note: Unless subscriptions: false is explicitly passed to the constructor parameters of new ApolloServer({ ... }), subscriptions are enabled by default, whether or not there is a Subscription type present in the schema. As an alternative to upgrading to a patched version, see the Workarounds section below to disable subscriptions if it is not necessary.

In cases where subscriptions: false is not explicitly set, the subscription server is impacted since validation rules which are enforced on the main request pipeline within Apollo Server were not being passed to the SubscriptionServer.create invocation (seen here, prior to the patch).

The omitted validation rules for the subscription server include any validationRules passed by implementors to the ApolloServer constructor which were expected to be enforced on the subscriptions WebSocket endpoint. Additionally, because an internal NoIntrospection validation rule is used to disable introspection, it would have been possible to introspect a server on the WebSocket endpoint that the SubscriptionServer creates even though it was not possible on other transports (e.g. HTTP).

The severity of risk depends on whether sensitive information is being stored in the schema itself. The contents of schema descriptions, or secrets which might be revealed by the names of types or field names within those types, will determine the risk to individual implementors.

Affected packages

The bug existed in apollo-server-core versions prior to version 2.14.2, however, this means all integration packages (e.g., apollo-server-express, etc.) prior to version 2.14.2 which depend on apollo-server-core for their subscriptions support are affected. This includes the apollo-server package that automatically provides an Express server.
... (truncated)
Affected versions: < 2.14.2

Changelog

Sourced from apollo-server-express's changelog.

v2.14.2

Note: This release is is related to a GitHub Security Advisory published by the Apollo Server team. Please read the attached advisory to understand the impact.

⚠️ SECURITY: Pass all schema validation rules to the subscription server, including validation rules that restrict introspection when introspection is meant to be disabled. Read the full GitHub Security Advisory for details.

v2.14.1

See complete versioning details.

apollo-server-testing: Ensure that user-provided context is cloned when using createTestClient, per the instructions in the intergration testing section of the Apollo Server documentation. [Issue #4170](apollographql/apollo-server#4170) [PR #4175](apollographql/apollo-server#4175)

v2.14.0

See complete versioning details.
apollo-server-core / apollo-server-plugin-base: Add support for willResolveField and corresponding end-handler within executionDidStart. This brings the remaining bit of functionality that was previously only available from graphql-extensions to the new plugin API. The graphql-extensions API (which was never documented) will be deprecated in Apollo Server 3.x. To see the documentation for the request pipeline API, see its documentation. For more details, see the attached PR. [PR #3988](apollographql/apollo-server#3988)

apollo-server-core: Deprecate graphql-extensions. All internal usages of the graphql-extensions API have been migrated to the request pipeline plugin API. For any implementor-supplied extensions, a deprecation warning will be printed once per-extension, per-server-startup, notifying of the intention to deprecate. Extensions should migrate to the plugin API, which is outlined in its documentation. [PR #4135](apollographql/apollo-server#4135)
apollo-engine-reporting: Currently only for non-federated graphs. Added an experimental schema reporting option, experimental_schemaReporting, for Apollo Graph Manager users. During this experiment, we'd appreciate testing and feedback from current and new users of the schema registry!

Prior to the introduction of this feature, the only way to get schemas into the schema registry in Apollo Graph Manager was to use the CLI and run apollo schema:push. Apollo schema reporting protocol is a new specification for GraphQL servers to automatically report schemas to the Apollo Graph Manager schema registry.

To enable schema reporting, provide a Graph Manager API key (available free from Apollo Graph Manager) in the APOLLO_KEY environment variable and set the experimental_schemaReporting option to true in the Apollo Server constructor options, like so:
const server = new ApolloServer({
  typeDefs,
  resolvers,
  engine: {
    experimental_schemaReporting: true,
    /* Other existing options can remain the same. */
  },
});
When enabled, a schema reporter is initiated by the apollo-engine-reporting agent. It will loop until the ApolloServer instance is stopped, periodically calling back to Apollo Graph Manager to send information. The life-cycle of this reporter is managed by the agent.

For more details on the implementation of this new protocol, see the PR which introduced it to Apollo Server and the preview documentation.
... (truncated)

Commits

a17f26b Release
7aaca56 Update @apollo/gateway and @apollo/federation CHANGELOG before publish.
354d991 Update CHANGELOG.md for subscription validation rules to Security Advisory.
04fab28 Merge remote-tracking branch 'origin/master' into advisory-fix-1
02f1fb6 chore(deps): update dependency gatsby to v2.22.15 (#4187)
eadbfc3 chore(deps): update dependency gatsby to v2.22.13 (#4181)
d979a9e chore(deps): update dependency @types/lodash to v4.14.154 (#4184)
68ff8e5 chore(deps): update dependency ioredis to v4.17.3 (#4182)
00a056a chore(deps): update dependency @types/lodash to v4.14.153 (#4180)
c0aa7c0 chore(deps): update dependency @azure/functions to v1.2.2 (#4179)
Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot merge will merge this PR after your CI passes on it
@dependabot squash and merge will squash and merge this PR after your CI passes on it
@dependabot cancel merge will cancel a previously requested merge and block automerging
@dependabot reopen will reopen this PR if it is closed
@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
@dependabot use these labels will set the current labels as the default for future PRs for this repo and language
@dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
@dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
@dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
@dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

Update frequency (including time of day and day of week)
Pull request limits (per update run and/or open at any time)
Out-of-range updates (receive only lockfile updates, if desired)
Security updates (receive only security updates, if desired)

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/moollaza/repo-remover/pull/130 **Author:** [@dependabot-preview[bot]](https://github.com/apps/dependabot-preview) **Created:** 6/5/2020 **Status:** ❌ Closed **Base:** `master` ← **Head:** `dependabot/npm_and_yarn/apollo-server-express-2.14.2` --- ### 📝 Commits (1) - [`a3427c5`](https://github.com/moollaza/repo-remover/commit/a3427c54b4b5b20ca34e18a300ee3ff92e67a63d) [Security] Bump apollo-server-express from 2.9.14 to 2.14.2 ### 📊 Changes **1 file changed** (+497 additions, -297 deletions) <details> <summary>View changed files</summary> 📝 `yarn.lock` (+497 -297) </details> ### 📄 Description Bumps [apollo-server-express](https://github.com/apollographql/apollo-server) from 2.9.14 to 2.14.2. **This update includes a security fix.** <details> <summary>Vulnerabilities fixed</summary> Sourced from <a href="https://github.com/advisories/GHSA-w42g-7vfc-xf37">The GitHub Security Advisory Database</a>. <blockquote> Introspection in schema validation in Apollo Server We encourage all users of Apollo Server to read this advisory in its entirety to understand the impact. The Resolution section contains details on patched versions. <h3>Impact</h3> If <code>subscriptions: false</code> is passed to the <code>ApolloServer</code> constructor options, there is no impact. If implementors were not expecting validation rules to be enforced on the WebSocket subscriptions transport and are unconcerned about introspection being enabled on the WebSocket subscriptions transport (or were not expecting that), then this advisory is not applicable. If <code>introspection: true</code> is passed to the <code>ApolloServer</code> constructor options, the impact is limited to user-provided validation rules (i.e., using <code>validationRules</code>) since there would be no expectation that introspection was disabled. The enforcement of user-provided validation rules on the HTTP transport is working as intended and is unaffected by this advisory. Similarly, disabling introspection on the HTTP transport is working as intended and is unaffected by this advisory. <blockquote> Note: Unless <code>subscriptions: false</code> is explicitly passed to the constructor parameters of <code>new ApolloServer({ ... })</code>, subscriptions are enabled by default, whether or not there is a <code>Subscription</code> type present in the schema. As an alternative to upgrading to a patched version, see the Workarounds section below to disable subscriptions if it is not necessary. </blockquote> In cases where <code>subscriptions: false</code> is not explicitly set, the subscription server is impacted since validation rules which are enforced on the main request pipeline within Apollo Server were not being passed to the <code>SubscriptionServer.create</code> invocation (<a href="https://github.com/apollographql/apollo-server/blob/7d6f23443e52a90deb74f152f34bb76eea78ee19/packages/apollo-server-core/src/ApolloServer.ts#L677-L726">seen here, prior to the patch</a>). The omitted validation rules for the subscription server include any <code>validationRules</code> passed by implementors to the <code>ApolloServer</code> constructor which were expected to be enforced on the subscriptions WebSocket endpoint. Additionally, because an internal <a href="https://github.com/apollographql/apollo-server/blob/7d6f23443/packages/apollo-server-core/src/ApolloServer.ts#L77-L88"><code>NoIntrospection</code></a> validation rule is used to disable introspection, it would have been possible to introspect a server on the WebSocket endpoint that the <code>SubscriptionServer</code> creates even though it was not possible on other transports (e.g. HTTP). The severity of risk depends on whether sensitive information is being stored in the schema itself. The contents of schema descriptions, or secrets which might be revealed by the names of types or field names within those types, will determine the risk to individual implementors. <h3>Affected packages</h3> The bug existed in <code>apollo-server-core</code> versions prior to version 2.14.2, however, this means all integration packages (e.g., <code>apollo-server-express</code>, etc.) prior to version 2.14.2 which depend on <code>apollo-server-core</code> for their subscriptions support are affected. This includes the <code>apollo-server</code> package that automatically provides an Express server. </tr></table> ... (truncated) Affected versions: < 2.14.2 </blockquote> </details> <details> <summary>Changelog</summary> Sourced from <a href="https://github.com/apollographql/apollo-server/blob/master/CHANGELOG.md">apollo-server-express's changelog</a>. <blockquote> <h3>v2.14.2</h3> <blockquote> Note: This release is is related to a GitHub Security Advisory published by the Apollo Server team. Please read the attached advisory to understand the impact. </blockquote> <ul> <li>⚠️ SECURITY: Pass all schema validation rules to the subscription server, including validation rules that restrict introspection when introspection is meant to be disabled. <a href="https://github.com/apollographql/apollo-server/security/advisories/GHSA-w42g-7vfc-xf37">Read the full GitHub Security Advisory for details</a>.</li> </ul> <h3>v2.14.1</h3> <blockquote> <a href="https://github.com/apollographql/apollo-server/commit/2da65ef9204027e43baedf9ce385bb3794fd0c9b">See complete versioning details.</a> </blockquote> <ul> <li><code>apollo-server-testing</code>: Ensure that user-provided context is cloned when using <code>createTestClient</code>, per the instructions in the <a href="">intergration testing</a> section of the Apollo Server documentation. [Issue <a href="https://github-redirect.dependabot.com/apollographql/apollo-server/issues/4170">#4170</a>](<a href="https://github-redirect.dependabot.com/apollographql/apollo-server/issues/4170">apollographql/apollo-server#4170</a>) [PR <a href="https://github-redirect.dependabot.com/apollographql/apollo-server/issues/4175">#4175</a>](<a href="https://github-redirect.dependabot.com/apollographql/apollo-server/pull/4175">apollographql/apollo-server#4175</a>)</li> </ul> <h3>v2.14.0</h3> <blockquote> <a href="https://github.com/apollographql/apollo-server/commit/d159e320879f594ba2d04036e3e1aa0653ff164d">See complete versioning details.</a> </blockquote> <ul> <li> <code>apollo-server-core</code> / <code>apollo-server-plugin-base</code>: Add support for <code>willResolveField</code> and corresponding end-handler within <code>executionDidStart</code>. This brings the remaining bit of functionality that was previously only available from <code>graphql-extensions</code> to the new plugin API. The <code>graphql-extensions</code> API (which was never documented) will be deprecated in Apollo Server 3.x. To see the documentation for the request pipeline API, see <a href="https://www.apollographql.com/docs/apollo-server/integrations/plugins/">its documentation</a>. For more details, see the attached PR. [PR <a href="https://github-redirect.dependabot.com/apollographql/apollo-server/issues/3988">#3988</a>](<a href="https://github-redirect.dependabot.com/apollographql/apollo-server/pull/3988">apollographql/apollo-server#3988</a>) </li> <li> <code>apollo-server-core</code>: Deprecate <code>graphql-extensions</code>. All internal usages of the <code>graphql-extensions</code> API have been migrated to the request pipeline plugin API. For any implementor-supplied <code>extensions</code>, a deprecation warning will be printed once per-extension, per-server-startup, notifying of the intention to deprecate. Extensions should migrate to the plugin API, which is outlined in <a href="https://www.apollographql.com/docs/apollo-server/integrations/plugins/">its documentation</a>. [PR <a href="https://github-redirect.dependabot.com/apollographql/apollo-server/issues/4135">#4135</a>](<a href="https://github-redirect.dependabot.com/apollographql/apollo-server/pull/4135">apollographql/apollo-server#4135</a>) </li> <li> <code>apollo-engine-reporting</code>: Currently only for non-federated graphs. Added an experimental schema reporting option, <code>experimental_schemaReporting</code>, for Apollo Graph Manager users. During this experiment, we'd appreciate testing and feedback from current and new users of the schema registry! Prior to the introduction of this feature, the only way to get schemas into the schema registry in Apollo Graph Manager was to use the CLI and run <code>apollo schema:push</code>. Apollo schema reporting protocol is a new specification for GraphQL servers to automatically report schemas to the Apollo Graph Manager schema registry. To enable schema reporting, provide a Graph Manager API key (available free from <a href="https://engine.apollographql.com/">Apollo Graph Manager</a>) in the <code>APOLLO_KEY</code> environment variable and set the <code>experimental_schemaReporting</code> option to <code>true</code> in the Apollo Server constructor options, like so: <pre lang="js"><code>const server = new ApolloServer({ typeDefs, resolvers, engine: { experimental_schemaReporting: true, /* Other existing options can remain the same. */ }, }); </code></pre> <blockquote> When enabled, a schema reporter is initiated by the <code>apollo-engine-reporting</code> agent. It will loop until the <code>ApolloServer</code> instance is stopped, periodically calling back to Apollo Graph Manager to send information. The life-cycle of this reporter is managed by the agent. </blockquote> For more details on the implementation of this new protocol, see the PR which introduced it to Apollo Server and the <a href="https://github.com/apollographql/apollo-schema-reporting-preview-docs">preview documentation</a>. </li> </ul> </tr></table> ... (truncated) </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/apollographql/apollo-server/commit/a17f26bf3ee2892f5c3751713cf59920049cc73a"><code>a17f26b</code></a> Release</li> <li><a href="https://github.com/apollographql/apollo-server/commit/7aaca5697eeba16547b81482cf8cfa93a6642a43"><code>7aaca56</code></a> Update <code>@apollo/gateway</code> and <code>@apollo/federation</code> CHANGELOG before publish.</li> <li><a href="https://github.com/apollographql/apollo-server/commit/354d9910e1c87af93c7d50263a28554b449e48db"><code>354d991</code></a> Update CHANGELOG.md for subscription validation rules to Security Advisory.</li> <li><a href="https://github.com/apollographql/apollo-server/commit/04fab282249b911a2ffb8e576d4d821dcf39c78d"><code>04fab28</code></a> Merge remote-tracking branch 'origin/master' into advisory-fix-1</li> <li><a href="https://github.com/apollographql/apollo-server/commit/02f1fb6498206ac7d8fdd5b1de7e509d483be5bf"><code>02f1fb6</code></a> chore(deps): update dependency gatsby to v2.22.15 (<a href="https://github-redirect.dependabot.com/apollographql/apollo-server/issues/4187">#4187</a>)</li> <li><a href="https://github.com/apollographql/apollo-server/commit/eadbfc38dd20ca9b5250d81c3ddbb1c772c93571"><code>eadbfc3</code></a> chore(deps): update dependency gatsby to v2.22.13 (<a href="https://github-redirect.dependabot.com/apollographql/apollo-server/issues/4181">#4181</a>)</li> <li><a href="https://github.com/apollographql/apollo-server/commit/d979a9ef8555db85310cb75c297092b48b051a55"><code>d979a9e</code></a> chore(deps): update dependency @types/lodash to v4.14.154 (<a href="https://github-redirect.dependabot.com/apollographql/apollo-server/issues/4184">#4184</a>)</li> <li><a href="https://github.com/apollographql/apollo-server/commit/68ff8e5c61206e4ee07249f63ca358b66bb606dc"><code>68ff8e5</code></a> chore(deps): update dependency ioredis to v4.17.3 (<a href="https://github-redirect.dependabot.com/apollographql/apollo-server/issues/4182">#4182</a>)</li> <li><a href="https://github.com/apollographql/apollo-server/commit/00a056a9e1d5a641bda48ae3924b23cbbb9600c8"><code>00a056a</code></a> chore(deps): update dependency @types/lodash to v4.14.153 (<a href="https://github-redirect.dependabot.com/apollographql/apollo-server/issues/4180">#4180</a>)</li> <li><a href="https://github.com/apollographql/apollo-server/commit/c0aa7c0bd28eda5a2fc538952695b3e6eeb653ff"><code>c0aa7c0</code></a> chore(deps): update dependency @azure/functions to v1.2.2 (<a href="https://github-redirect.dependabot.com/apollographql/apollo-server/issues/4179">#4179</a>)</li> <li>Additional commits viewable in <a href="https://github.com/apollographql/apollo-server/compare/apollo-server-express@2.9.14...apollo-server-express@2.14.2">compare view</a></li> </ul> </details> [![Dependabot compatibility score](https://api.dependabot.com/badges/compatibility_score?dependency-name=apollo-server-express&package-manager=npm_and_yarn&previous-version=2.9.14&new-version=2.14.2)](https://dependabot.com/compatibility-score/?dependency-name=apollo-server-express&package-manager=npm_and_yarn&previous-version=2.9.14&new-version=2.14.2) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired) </details> --- 🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.