fix(deps): update dependency gatsby to v4 [security] #303

renovate · 2024-06-23T21:46:08Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
gatsby (source, changelog)	`^3.14.6` -> `^4.0.0`

GitHub Vulnerability Alerts

CVE-2023-34238

Impact

The Gatsby framework prior to versions 4.25.7 and 5.9.1 contain a Local File Inclusion vulnerability in the __file-code-frame and __original-stack-frame paths, exposed when running the Gatsby develop server (gatsby develop).

The following steps can be used to reproduce the vulnerability:


# Create a new Gatsby project
$ npm init gatsby
$ cd my-gatsby-site

# Start the Gatsby develop server
$ gatsby develop

# Execute the Local File Inclusion vulnerability in __file-code-frame
$ curl "http://127.0.0.1:8000/__file-code-frame?filePath=/etc/passwd&lineNumber=1"

# Execute the Local File Inclusion vulnerability in __original-stack-frame
$ curl "http://127.0.0.1:8000/__original-stack-frame?moduleId=/etc/hosts&lineNumber=1&skipSourceMap=1"

It should be noted that by default gatsby develop is only accessible via the localhost 127.0.0.1, and one would need to intentionally expose the server to other interfaces to exploit this vulnerability by using server options such as --host 0.0.0.0, -H 0.0.0.0, or the GATSBY_HOST=0.0.0.0 environment variable.

Patches

A patch has been introduced in [email protected] and [email protected] which mitigates the issue.

Workarounds

As stated above, by default gatsby develop is only exposed to the localhost 127.0.0.1. For those using the develop server in the default configuration no risk is posed. If other ranges are required, preventing the develop server from being exposed to untrusted interfaces or IP address ranges would mitigate the risk from this vulnerability.

We encourage projects to upgrade to the latest major release branch for all Gatsby plugins to ensure the latest security updates and bug fixes are received in a timely manner.

Credits

We would like to thank Maxwell Garrett of Assetnote for bringing the __file-code-frame issue to our attention.

For more information

Email us at [email protected].

Release Notes

gatsbyjs/gatsby (gatsby)

Welcome to [email protected] release (September 2022 #2)

Key highlights of this release:

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

Full changelog

`v4.23.1`

Compare Source

`v4.23.0`: v4.23

Compare Source

Welcome to [email protected] release (September 2022 #1)

Key highlights of this release:

Open RFCs

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

Full changelog

`v4.22.1`

Compare Source

`v4.22.0`: v4.22

Compare Source

Welcome to [email protected] release (August 2022 #3)

Key highlights of this release:

Open RFCs

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

Full changelog

`v4.21.1`

Compare Source

`v4.21.0`: v4.21

Compare Source

Welcome to [email protected] release (August 2022 #2)

Key highlights of this release:

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

Full changelog

`v4.20.0`: v4.20

Compare Source

Welcome to [email protected] release (August 2022 #1)

Key highlights of this release:

RFC for changes in sort and aggregation fields in Gatsby GraphQL Schema
Release Candidate for gatsby-plugin-mdx v4 - Support for MDX v2 and more!

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

Full changelog

`v4.19.2`

Compare Source

`v4.19.1`

Compare Source

`v4.19.0`: v4.19

Compare Source

Welcome to [email protected] release (July 2022 #2)

Key highlights of this release:

Gatsby Head API - Better performance & more future-proof than react-helmet
Release Candidate for gatsby-plugin-mdx v4 - Support for MDX v2 and more!

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

Full changelog

`v4.18.2`

Compare Source

`v4.18.1`

Compare Source

`v4.18.0`: v4.18

Compare Source

Welcome to [email protected] release (July 2022 #1)

Key highlights of this release:

typesOutputPath option for GraphQL Typegen - Configure the location of the generated TypeScript types
Server Side Rendering (SSR) in development - Find bugs & hydration errors more easily during gatsby develop
Open RFCs - MDX v2 & Metadata management

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

Full changelog

`v4.17.2`

Compare Source

`v4.17.1`

Compare Source

`v4.17.0`: v4.17

Compare Source

Welcome to [email protected] release (June 2022 #2)

Key highlights of this release:

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

Full changelog

`v4.16.0`: v4.16

Compare Source

Welcome to [email protected] release (June 2022 #1)

Key highlights of this release:

Also check out notable bugfixes.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

Full changelog

`v4.15.2`

Compare Source

`v4.15.1`

Compare Source

`v4.15.0`: v4.15

Compare Source

Welcome to [email protected] release (May 2022 #2)

Key highlights of this release:

Also check out notable bugfixes.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

[Full changelog][full-changelog]

`v4.14.1`

Compare Source

`v4.14.0`: v4.14

Compare Source

Welcome to [email protected] release (May 2022 #1)

Key highlights of this release:

Also check out notable bugfixes.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

Full changelog

`v4.13.1`

Compare Source

`v4.13.0`: v4.13

Compare Source

Welcome to [email protected] release (April 2022 #2)

Key highlights of this release:

Also check out notable bugfixes.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know
if you have any issues.

Previous release notes

Full changelog

`v4.12.1`

Compare Source

`v4.12.0`: v4.12

Compare Source

Welcome to [email protected] release (April 2022 #1)

Key highlights of this release:

New RFCs

Also check out notable bugfixes.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know
if you have any issues.

Previous release notes

Full changelog

`v4.11.3`

Compare Source

`v4.11.2`

Compare Source

`v4.11.1`

Compare Source

`v4.11.0`: v4.11

Compare Source

Welcome to [email protected] release (March 2022 #3)

Key highlights of this release:

Also check out notable bugfixes.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know
if you have any issues.

Previous release notes

Full changelog

`v4.10.3`

Compare Source

`v4.10.2`

Compare Source

`v4.10.1`

Compare Source

`v4.10.0`: v4.10

Compare Source

Welcome to [email protected] release (March 2022 #2)

Key highlights of this release:

Image CDN

Also check out notable bugfixes.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know
if you have any issues.

Previous release notes

Full changelog

`v4.9.3`

Compare Source

`v4.9.2`

Compare Source

`v4.9.1`

Compare Source

`v4.9.0`: v4.9

Compare Source

Welcome to [email protected] release (March 2022 #1)

Key highlights of this release:

Support for TypeScript in gatsby-config and gatsby-node

Also check out notable bugfixes.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know if you have any issues.

Previous release notes

Full changelog

`v4.8.2`

Compare Source

`v4.8.1`

Compare Source

`v4.8.0`: v4.8

Compare Source

Welcome to [email protected] release (February 2022 #2)

Key highlights of this release:

Also check out notable bugfixes.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know
if you have any issues.

Previous release notes

Full changelog

`v4.7.2`

Compare Source

`v4.7.1`

Compare Source

`v4.7.0`: v4.7

Compare Source

Welcome to [email protected] release (February 2022 #1)

Key highlights of this release:

trailingSlash Option - Now built into the Framework itself
Faster Schema Creation & createPages - Speed improvements of at least 30%

Also check out notable bugfixes.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know
if you have any issues.

Previous release notes

Full changelog

`v4.6.2`

Compare Source

`v4.6.1`

Compare Source

`v4.6.0`: v4.6

Compare Source

Welcome to [email protected] release (January 2022 #2)

Key highlights of this release:

Also check out notable bugfixes.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know
if you have any issues.

Previous release notes

Full changelog

`v4.5.5`

Compare Source

`v4.5.4`

Compare Source

`v4.5.3`

Compare Source

`v4.5.2`

Compare Source

`v4.5.1`

Compare Source

`v4.5.0`: v4.5

Compare Source

Welcome to [email protected] release (January 2022 #1)

Key highlights of this release:

Also check out notable bugfixes.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know
if you have any issues.

Previous release notes

Full changelog

`v4.4.0`: v4.4

Compare Source

Welcome to [email protected] release (December 2021 #1)

Key highlights of this release:

Detect Node Mutations

Also check out notable bugfixes.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know
if you have any issues.

Previous release notes

Full changelog

`v4.3.0`: v4.3

Compare Source

Welcome to [email protected] release (November 2021 #3)

Key highlights of this release:

Also check out notable bugfixes.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know
if you have any issues.

Previous release notes

Full changelog

`v4.2.0`: v4.2

Compare Source

Welcome to [email protected] release (November 2021 #2).

Key highlights of this release:

Also check out notable bugfixes.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know
if you have any issues.

Previous release notes

Full changelog

`v4.1.6`

Compare Source

`v4.1.5`

Compare Source

`v4.1.4`

Compare Source

`v4.1.3`

Compare Source

`v4.1.2`

Compare Source

`v4.1.1`

Compare Source

`v4.1.0`: v4.1

Compare Source

Welcome to [email protected] release (November 2021 #1).

Key highlights of this release:

Also check out notable bugfixes.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know
if you have any issues.

Previous release notes

Full changelog

`v4.0.2`

Compare Source

`v4.0.1`

Compare Source

`v4.0.0`: v4.0.0

Compare Source

Welcome to [email protected] release (October 2021 #1).

We've released Gatsby 3 in March 2021 and now have a lot of exciting new features for Gatsby 4!
We’ve tried to make migration smooth. Please refer to the migration guide
and let us know if you encounter any issues when migrating.

Key highlights of this release:

Parallel Query Running - up to 40% reduction in build times
Deferred Static Generation (DSG) - defer page generation to user request, speeding up build times
Server-Side Rendering (SSR) - pre-render a page with data that is fetched when a user visits the page

Also check out notable bugfixes and improvements.

Bleeding Edge: Want to try new features as soon as possible? Install gatsby@next and let us know
if you have any issues.

Previous release notes for 3.14

Full changelog

Configuration

📅 Schedule: Branch creation - "" in timezone America/New_York, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

renovate · 2024-06-23T21:46:09Z

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm warn ERESOLVE overriding peer dependency
npm warn While resolving: [email protected]
npm warn Found: [email protected]
npm warn node_modules/gatsby
npm warn   gatsby@"^4.0.0" from the root project
npm warn   2 more (gatsby-plugin-alias-imports, gatsby-plugin-env-variables)
npm warn
npm warn Could not resolve dependency:
npm warn peer gatsby@"^3.0.0-next.0" from [email protected]
npm warn node_modules/babel-plugin-remove-graphql-queries
npm warn   babel-plugin-remove-graphql-queries@"^3.15.0" from [email protected]
npm warn   node_modules/gatsby-plugin-typescript
npm warn
npm warn Conflicting peer dependency: [email protected]
npm warn node_modules/gatsby
npm warn   peer gatsby@"^3.0.0-next.0" from [email protected]
npm warn   node_modules/babel-plugin-remove-graphql-queries
npm warn     babel-plugin-remove-graphql-queries@"^3.15.0" from [email protected]
npm warn     node_modules/gatsby-plugin-typescript
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/gatsby
npm error   gatsby@"^4.0.0" from the root project
npm error   peer gatsby@">2.0.0" from [email protected]
npm error   node_modules/gatsby-plugin-alias-imports
npm error     gatsby-plugin-alias-imports@"^1.0.5" from the root project
npm error   1 more (gatsby-plugin-env-variables)
npm error
npm error Could not resolve dependency:
npm error peer gatsby@"^3.0.0-next.0" from [email protected]
npm error node_modules/gatsby-plugin-react-helmet
npm error   gatsby-plugin-react-helmet@"^4.14.0" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/gatsby
npm error   peer gatsby@"^3.0.0-next.0" from [email protected]
npm error   node_modules/gatsby-plugin-react-helmet
npm error     gatsby-plugin-react-helmet@"^4.14.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-12-02T10_06_26_849Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-12-02T10_06_26_849Z-debug-0.log

renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch 3 times, most recently from e99a79a to 4802ce9 Compare July 15, 2024 11:25

renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch 2 times, most recently from f27ed14 to ac34cee Compare July 22, 2024 09:45

renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch 2 times, most recently from 5a2a2ef to aebedd6 Compare July 31, 2024 14:17

renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch 2 times, most recently from 12ed94c to a65163e Compare August 19, 2024 06:37

renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from a65163e to e6a9d4e Compare August 19, 2024 11:44

renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch 6 times, most recently from b67948e to 2586ee9 Compare September 9, 2024 10:50

renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch 3 times, most recently from 6631378 to 93ab497 Compare September 16, 2024 09:09

renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch 4 times, most recently from b69f34e to 637e967 Compare September 30, 2024 09:15

renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch 3 times, most recently from 25ff29e to ef7f9eb Compare October 14, 2024 06:06

renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from ef7f9eb to b413f94 Compare October 14, 2024 09:38

renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from b413f94 to 9037a04 Compare October 21, 2024 10:40

renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from 9037a04 to e477884 Compare October 31, 2024 18:49

renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch 2 times, most recently from 2ae2c62 to 87c5a26 Compare November 11, 2024 09:29

renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from 87c5a26 to fc107c5 Compare November 18, 2024 10:51

renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from fc107c5 to a210bbc Compare November 25, 2024 11:55

fix(deps): update dependency gatsby to v4 [security]

1380726

renovate bot force-pushed the renovate/npm-gatsby-vulnerability branch from a210bbc to 1380726 Compare December 2, 2024 10:07

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

fix(deps): update dependency gatsby to v4 [security] #303

fix(deps): update dependency gatsby to v4 [security] #303

renovate bot commented Jun 23, 2024 •

edited

Loading

renovate bot commented Jun 23, 2024 •

edited

Loading

fix(deps): update dependency gatsby to v4 [security] #303

Are you sure you want to change the base?

fix(deps): update dependency gatsby to v4 [security] #303

Conversation

renovate bot commented Jun 23, 2024 • edited Loading

GitHub Vulnerability Alerts

Impact

Patches

Workarounds

Credits

For more information

Release Notes

v4.24.0: v4.24

v4.23.0: v4.23

v4.22.0: v4.22

v4.21.0: v4.21

v4.20.0: v4.20

v4.19.0: v4.19

v4.18.0: v4.18

v4.17.0: v4.17

v4.16.0: v4.16

v4.15.0: v4.15

v4.14.0: v4.14

v4.13.0: v4.13

v4.12.0: v4.12

v4.11.0: v4.11

v4.10.0: v4.10

v4.9.0: v4.9

v4.8.0: v4.8

v4.7.0: v4.7

v4.6.0: v4.6

v4.5.0: v4.5

v4.4.0: v4.4

v4.3.0: v4.3

v4.2.0: v4.2

v4.1.0: v4.1

v4.0.0: v4.0.0

Configuration

renovate bot commented Jun 23, 2024 • edited Loading

⚠️ Artifact update problem

File name: package-lock.json

renovate bot commented Jun 23, 2024 •

edited

Loading

`v4.24.0`: v4.24

`v4.23.0`: v4.23

`v4.22.0`: v4.22

`v4.21.0`: v4.21

`v4.20.0`: v4.20

`v4.19.0`: v4.19

`v4.18.0`: v4.18

`v4.17.0`: v4.17

`v4.16.0`: v4.16

`v4.15.0`: v4.15

`v4.14.0`: v4.14

`v4.13.0`: v4.13

`v4.12.0`: v4.12

`v4.11.0`: v4.11

`v4.10.0`: v4.10

`v4.9.0`: v4.9

`v4.8.0`: v4.8

`v4.7.0`: v4.7

`v4.6.0`: v4.6

`v4.5.0`: v4.5

`v4.4.0`: v4.4

`v4.3.0`: v4.3

`v4.2.0`: v4.2

`v4.1.0`: v4.1

`v4.0.0`: v4.0.0

renovate bot commented Jun 23, 2024 •

edited

Loading