GHSA-j5g3-5c8r-7qfx: @apollo/server Prevent Logging Invalid Header Values Vulnerability

LOW
Published
Advisory Summary

GHSA-j5g3-5c8r-7qfx is a LOW prevent logging invalid header values vulnerability (General Security Weakness) affecting @apollo/server libraries in the npm ecosystem. The issue involves prevent logging invalid header values. Remediation is available by upgrading affected packages to version 4.9.3, 3.12.1, 2.26.1.

GHSA-j5g3-5c8r-7qfx at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-j5g3-5c8r-7qfx
Severity LOW
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product @apollo/server
Package Ecosystem npm
Published Date
Last Updated

How to Fix GHSA-j5g3-5c8r-7qfx

To remediate this vulnerability, upgrade all affected @apollo/server 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/server fixed: 4.9.3
npm install @apollo/server@4.9.3
apollo-server-core fixed: 3.12.1
npm install apollo-server-core@3.12.1
apollo-server-core fixed: 2.26.1
npm install apollo-server-core@2.26.1
Verify Direct and Transitive Dependencies

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

npm ls @apollo/server

How to Check if You Are Affected

To determine whether your Node.js application is affected by GHSA-j5g3-5c8r-7qfx, inspect your project dependencies using npm:

npm ls @apollo/server

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

Note: The npm ls @apollo/server command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In @apollo/server, 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 ### What kind of vulnerability is it? Apollo Server can log sensitive information (Studio API keys) if they are passed incorrectly (with leading/trailing whitespace) or if they have any characters that are invalid as part of a header value. ### Who is impacted? Users who (all of the below): * use either the schema reporting or usage reporting feature * use an Apollo Studio API key which has invalid header values * use the default fetcher (`node-fetch`) or configured their own `node-fetch` fetcher The following node snippet can test whether your API key has invalid header values. This code is taken directly from `node-fetch@2`'s header value validation code. ```js const invalidHeaderCharRegex = /[^\t\x20-\x7e\x80-\xff]/; if (invalidHeaderCharRegex.test('<YOUR_API_KEY>')) { console.log('potentially affected'); } console.log('unaffected'); ``` If the provided API key is not a valid header value, whenever Apollo Server uses that API key in a request (to Studio, for example), `node-fetch` will throw an error _which contains the header value_. This error is logged in various ways depending on the user's configuration, but most likely the console or some configured logging service. ### Patches This problem is patched in the latest version of Apollo Server as soon as this advisory is published. ### Workarounds * Try retrieving a new API key from Studio. Note: this may not work if the invalid character is not part of the secret (it may be derived from identifiers like graph name, user name). * Override the `fetcher` * Disable schema reporting and/or usage reporting ### Solution * Apollo Server will now call `.trim()` on incoming API keys in order to eliminate leading/trailing whitespace and log a warning when it does so. * Apollo Server will now perform the same validation of API keys as `node-fetch@2` performs on header values on startup. Apollo Server will throw an error on startup (i.e., fail to start completely) and notify the user their API key is invalid along with the offending characters.

GHSA-j5g3-5c8r-7qfx Affected @apollo/server Versions

3 component(s)
Fixed Versions:
4.9.33.12.12.26.1
Product / Package Ecosystem Affected Versions Fixed Version
@apollo/server
npm
< 4.9.3
4.9.3
apollo-server-core
npm
≥ 3.0.0
< 3.12.1
3.12.1
apollo-server-core
npm
< 2.26.1
2.26.1

References

Frequently Asked Questions

What is GHSA-j5g3-5c8r-7qfx?
GHSA-j5g3-5c8r-7qfx is a security vulnerability in @apollo/server involving Prevent logging invalid header values under General Security Weakness.
Which @apollo/server versions are affected?
Affected versions include releases prior to 4.9.3, 3.12.1, 2.26.1 across affected packages: @apollo/server, apollo-server-core.
What version fixes GHSA-j5g3-5c8r-7qfx?
Upgrading to 4.9.3, 3.12.1, 2.26.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is @apollo/server affected?
Yes, @apollo/server is affected in releases prior to 4.9.3. Upgrade your dependency to 4.9.3 or later.
Is apollo-server-core affected?
Yes, apollo-server-core is affected in releases prior to 3.12.1, 2.26.1. Upgrade your dependency to 3.12.1, 2.26.1 or later.
What CWE is associated with GHSA-j5g3-5c8r-7qfx?
GHSA-j5g3-5c8r-7qfx is classified under General Security Weakness.
How can I check npm dependencies for GHSA-j5g3-5c8r-7qfx?
Run the dependency tree command: 'npm ls @apollo/server'. 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-j5g3-5c8r-7qfx",
  "modified" : "2023-08-30T21:24:57Z",
  "published" : "2023-08-30T21:24:57Z",
  "aliases" : [ ],
  "summary" : "Prevent logging invalid header values",
  "details" : "## Impact\n### What kind of vulnerability is it?\nApollo Server can log sensitive information (Studio API keys) if they are passed incorrectly (with leading/trailing whitespace) or if they have any characters that are invalid as part of a header value.\n\n### Who is impacted?\nUsers who (all of the below):\n* use either the schema reporting or usage reporting feature\n* use an Apollo Studio API key which has invalid header values\n* use the default fetcher (`node-fetch`) or configured their own `node-fetch` fetcher\n\nThe following node snippet can test whether your API key has invalid header values. This code is taken directly from `node-fetch@2`'s header value validation code.\n```js\nconst invalidHeaderCharRegex = /[^\\t\\x20-\\x7e\\x80-\\xff]/;\nif (invalidHeaderCharRegex.test('<YOUR_API_KEY>')) {\n  console.log('potentially affected');\n}\nconsole.log('unaffected');\n```\n\nIf the provided API key is not a valid header value, whenever Apollo Server uses that API key in a request (to Studio, for example), `node-fetch` will throw an error _which contains the header value_. This error is logged in various ways depending on the user's configuration, but most likely the console or some configured logging service.\n\n### Patches\nThis problem is patched in the latest version of Apollo Server as soon as this advisory is published.\n\n### Workarounds\n* Try retrieving a new API key from Studio. Note: this may not work if the invalid character is not part of the secret (it may be derived from identifiers like graph name, user name).\n* Override the `fetcher` \n* Disable schema reporting and/or usage reporting\n\n### Solution\n* Apollo Server will now call `.trim()` on incoming API keys in order to eliminate leading/trailing whitespace and log a warning when it does so.\n* Apollo Server will now perform the same validation of API keys as `node-fetch@2` performs on header values on startup. Apollo Server will throw an error on startup (i.e., fail to start completely) and notify the user their API key is invalid along with the offending characters.",
  "severity" : [ ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@apollo/server"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "4.9.3"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "apollo-server-core"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.0.0"
      }, {
        "fixed" : "3.12.1"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "apollo-server-core"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.26.1"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/apollographql/apollo-server/security/advisories/GHSA-j5g3-5c8r-7qfx"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/apollographql/apollo-server/commit/2c8106c433c4add4b43e2e2b2f5c5c4887b17314"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/apollographql/apollo-server/commit/d38b43bac88acdef4295759d7dcc3d4c348d9575"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/apollographql/apollo-server"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2023-08-30T21:24:57Z",
    "nvd_published_at" : null
  }
}