Skip to content
Noroxi
OSV ecosystem advisory

GHSA-w42g-7vfc-xf37: Introspection in schema validation in Apollo Server

Medium—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Fixed version: apollo-server (npm) 2.14.2; apollo-server-azure-functions (npm) 2.14.2; apollo-server-cache-memcached (npm) 2.14.2.

Low priority for now. Upgrade to apollo-server (npm) 2.14.2; apollo-server-azure-functions (npm) 2.14.2; apollo-server-cache-memcached (npm) 2.14.2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: OSV

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](https://github.com/apollographql/apollo-server/blob/7d6f23443e52a90deb74f152f34bb76eea78ee19/packages/apollo-server-core/src/ApolloServer.ts#L677-L726)). 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`](https://github.com/apollographql/apollo-server/blob/7d6f23443/packages/apollo-server-core/src/ApolloServer.ts#L77-L88) 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. Therefore, for officially published Apollo Server packages, the full list of affected packages includes: `apollo-server`, `apollo-server-azure-functions`, `apollo-server-cache-memcached`, `apollo-server-core`, `apollo-server-cloud-functions`, `apollo-server-cloudflare`, `apollo-server-express`, `apollo-server-fastify`, `apollo-server-hapi`, `apollo-server-koa`, `apollo-server-lambda`, and `apollo-server-micro`. > Note: The full list included here doesn't fit into the box provided by the GitHub Security Advisories form. ### Resolution The problem is resolved in Apollo Server versions 2.14.2 or higher. If upgrading is not an option, see _Workarounds_ below. When upgrading, ensure that the affected integration package (e.g., `apollo-server-express`) **and** the `apollo-server-core` package are both updated to the patched versions. (The version numbers should both be 2.14.2.) ### Workarounds Upgrading to a patched version is the recommended solution. If upgrading is not an option, subscriptions can be disabled with `subscriptions: false` to resolve the impact. **Disabling subscriptions in this way will disable _all_ subscriptions support and the WebSocket transport**: ```js const server = new ApolloServer({ subscriptions: false, /* Other options, such as typeDefs, resolvers, schema, etc. */ }); ``` ### For more information If you have any questions or comments about this advisory, please [open an issue](https://github.com/apollographql/apollo-server/issues/new) and the maintainers will try to assist. ### Credit and appreciation Apollo fully believes in ethical disclosure of vulnerabilities by security researchers who notify us with details and provide us time to address and fix the issues before publicly disclosing. Credit for this discovery goes to the team at [Bitwala](https://www.bitwala.com/), who reported the concern to us responsibly after discovering it during their own auditing.

Published
Jun 5, 2020
Updated
Aug 31, 2020
EPSS
—
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · —

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow GHSA-w42g-7vfc-xf37

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
npmapollo-server
npmapollo-server-azure-functions
npmapollo-server-cache-memcached
npmapollo-server-core
npmapollo-server-cloud-functions
npmapollo-server-cloudflare
npmapollo-server-express
npmapollo-server-fastify
npmapollo-server-hapi
npmapollo-server-koa
npmapollo-server-lambda
npmapollo-server-micro

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
npmapollo-serverbefore 2.14.22.14.2
npmapollo-server-azure-functionsbefore 2.14.22.14.2
npmapollo-server-cache-memcachedbefore 2.14.22.14.2
npmapollo-server-cloud-functionsbefore 2.14.22.14.2
npmapollo-server-cloudflarebefore 2.14.22.14.2
npmapollo-server-corebefore 2.14.22.14.2
npmapollo-server-expressbefore 2.14.22.14.2
npmapollo-server-fastifybefore 2.14.22.14.2
npmapollo-server-hapibefore 2.14.22.14.2
npmapollo-server-koabefore 2.14.22.14.2
npmapollo-server-lambdabefore 2.14.22.14.2
npmapollo-server-microbefore 2.14.22.14.2

Same product

npm: all records

Other highest-scoring records for the same primary product.

  • GHSA-2p3c-p3qw-69r4The graphql-upload library included in Apollo Server 2 is vulnerable to CSRF mutations
    0Monitor
  • GHSA-qm7x-rc44-rrqwCross-site Scripting Vulnerability in GraphQL Playground (distributed by Apollo Server)
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
npm:apollo-server2.14.2Package registry (OSV)
npm:apollo-server-azure-functions2.14.2Package registry (OSV)
npm:apollo-server-cache-memcached2.14.2Package registry (OSV)
npm:apollo-server-cloud-functions2.14.2Package registry (OSV)
npm:apollo-server-cloudflare2.14.2Package registry (OSV)
npm:apollo-server-core2.14.2Package registry (OSV)
npm:apollo-server-express2.14.2Package registry (OSV)
npm:apollo-server-fastify2.14.2Package registry (OSV)
npm:apollo-server-hapi2.14.2Package registry (OSV)
npm:apollo-server-koa2.14.2Package registry (OSV)
npm:apollo-server-lambda2.14.2Package registry (OSV)
npm:apollo-server-micro2.14.2Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

All records