Update dependency gatsby-plugin-mdx to v3.15.2 [SECURITY]

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
gatsby-plugin-mdx (source)	3.11.1 -> 3.15.2

GitHub Vulnerability Alerts

CVE-2022-25863

Impact

The gatsby-plugin-mdx plugin prior to versions 3.15.2 and 2.14.1 passes input through to the gray-matter npm package, which is vulnerable to JavaScript injection in its default configuration, unless input is sanitized. The vulnerability is present when passing input in both webpack (MDX files in src/pages or MDX file imported as component in frontend / React code) and data mode (querying MDX nodes via GraphQL). Injected JavaScript executes in the context of the build server.

To exploit this vulnerability untrusted/unsanitized input would need to be sourced or added into an MDX file. The following MDX payload demonstrates a vulnerable configuration:

---js
((require("child_process")).execSync("id >> /tmp/rce"))
--- 

Patches

A patch has been introduced in [email protected] and [email protected] which mitigates the issue by disabling the gray-matter JavaScript Frontmatter engine. The patch introduces a new option, JSFrontmatterEngine which is set to false by default. When setting JSFrontmatterEngine to true, input passed to gatsby-plugin-mdx must be sanitized before processing to avoid a security risk. Warnings are displayed when enabling JSFrontmatterEngine to true or if it appears that the MDX input is attempting to use the Frontmatter engine.

Workarounds

If an older version of gatsby-plugin-mdx must be used, input passed into the plugin should be sanitized ahead of processing.

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 Snyk [snyk.io] for initially bringing the issue to our attention, as well as Feng Xiao and Zhongfu Su, who reported the issue to Snyk.

For more information

Email us at [email protected].

---

Release Notes

gatsbyjs/gatsby

v3.15.2

Compare Source

Bug Fixes

• don't allow JS frontmatter by default #​35830 #​35832 (e916cf8)

v3.15.1

Compare Source

Note: Version bump only for package gatsby-plugin-mdx

v3.15.0

Compare Source

🧾 Release notes

Note: Version bump only for package gatsby-plugin-mdx

v3.14.0

Compare Source

🧾 Release notes

Bug Fixes

• update dependency fs-extra to ^10.1.0 #​34976 (10752ed)
• update dependency core-js to ^3.22.3 #​35541 (1a4d0ea)
• update dependency core-js to ^3.22.2 #​33381 (f4a7ca5)

v3.13.0

Compare Source

🧾 Release notes

Note: Version bump only for package gatsby-plugin-mdx

3.12.1 (2022-04-13)

Note: Version bump only for package gatsby-plugin-mdx

v3.12.1

Compare Source

Note: Version bump only for package gatsby-plugin-mdx

v3.12.0

Compare Source

🧾 Release notes

Note: Version bump only for package gatsby-plugin-mdx

3.11.1 (2022-03-31)

Note: Version bump only for package gatsby-plugin-mdx

---

Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

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

♻ Rebasing: Whenever PR becomes conflicted, 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 has been generated by Mend Renovate. View repository job log here.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (3.15.2). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.