Releases: apollographql/apollo-server
@apollo/[email protected]
@apollo/[email protected]
Patch Changes
- Updated dependencies [
41f98d4]:- @apollo/[email protected]
@apollo/[email protected]
Minor Changes
- #8054
89e3f84Thanks @clenfest! - Adds a new graphql-js validation rule to reject operations that recursively request selections above a specified maximum, which is disabled by default. Use configuration optionmaxRecursiveSelections=trueto enable with a maximum of 10,000,000, ormaxRecursiveSelections=<number>for a custom maximum. Enabling this validation can help avoid performance issues with configured validation rules or plugins.
Patch Changes
- #8031
2550d9fThanks @slagiewka! - Add return after sending 400 response in doubly escaped JSON parser middleware
@apollo/[email protected]
Patch Changes
- Updated dependencies [
89e3f84,2550d9f]:- @apollo/[email protected]
@apollo/[email protected]
@apollo/[email protected]
@apollo/[email protected]
@apollo/[email protected]
(No change; there is a change to the @apollo/server-integration-testsuite used to test integrations, and the two packages always have matching versions.)
@apollo/[email protected]
Patch Changes
-
#7952
bb81b2cThanks @glasser! - Upgrade dependencies so that automated scans don't detect a vulnerability.@apollo/serverdepends onexpresswhich depends oncookie. Versions ofexpressolder than v4.21.1 depend on a version ofcookievulnerable to CVE-2024-47764. Users of olderexpressversions who callres.cookie()orres.clearCookie()may be vulnerable to this issue.However, Apollo Server does not call this function directly, and it does not expose any object to user code that allows TypeScript users to call this function without an unsafe cast.
The only way that this direct dependency can cause a vulnerability for users of Apollo Server is if you call
startStandaloneServerwith a context function that calls Express-specific methods such asres.cookie()orres.clearCookies()on the response object, which is a violation of the TypeScript types provided bystartStandaloneServer(which only promise that the response object is a core Node.jshttp.ServerResponserather than the Express-specific subclass). So this vulnerability can only affect Apollo Server users who use unsafe JavaScript or unsafeastypecasts in TypeScript.However, this upgrade will at least prevent vulnerability scanners from alerting you to this dependency, and we encourage all Express users to upgrade their project's own
expressdependency to v4.21.1 or newer.