fix(deps): update dependency superjson to v1.8.1 [security]

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
superjson	1.8.0 -> 1.8.1

GitHub Vulnerability Alerts

CVE-2022-23631

Impact

This is critical vulnerability, as it allows to run arbitrary code on any server using superjson input, including a Blitz.js server, without prior authentication or knowledge. Attackers gain full control over the server so they could steal and manipulate data or attack further systems. The only requirement is that the server implements at least one endpoint which uses superjson during request processing. In the case of Blitz.js, it would be at least one RPC call.

Patches

This has been patched in superjson 1.8.1 and Blitz.js 0.45.3.

If you are unable to upgrade to Blitz.js 0.45.3 in a timely manner, you can instead upgrade only superjson to version 1.8.1 using yarn resolutions are similar. Blitz versions < 0.45.3 are only affected because they used superjson versions < 1.8.1.

Workarounds

None

For more information

If you have any questions or comments about this advisory:

• Open an issue in https://github.com/blitz-js/superjson
• Email us at b@bayer.ws

References

• https://www.sonarsource.com/blog/blitzjs-prototype-pollution/

---

Release Notes

blitz-js/superjson (superjson)

v1.8.1

Compare Source

Fix a critical security vulnerability. See CVE-2022-23631 for more details.

---

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 was generated by Mend Renovate. View the repository job log.

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/prisma/ama-prisma/6Ac3V3USKFvrLEU4CFbtPKG53uPJ
✅ Preview: Failed

[renovate]

⚠ 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 ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @next-auth/prisma-adapter@0.5.2-next.15
npm ERR! Found: next-auth@4.0.0-next.26
npm ERR! node_modules/next-auth
npm ERR!   next-auth@"4.0.0-next.26" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer next-auth@">=4" from @next-auth/prisma-adapter@0.5.2-next.15
npm ERR! node_modules/@next-auth/prisma-adapter
npm ERR!   @next-auth/prisma-adapter@"0.5.2-next.15" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: next-auth@4.10.3
npm ERR! node_modules/next-auth
npm ERR!   peer next-auth@">=4" from @next-auth/prisma-adapter@0.5.2-next.15
npm ERR!   node_modules/@next-auth/prisma-adapter
npm ERR!     @next-auth/prisma-adapter@"0.5.2-next.15" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate-cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2022-08-03T15_57_19_435Z-debug-0.log

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
ama-prisma	✅ Ready (Inspect)	Visit Preview	Aug 3, 2022 at 4:04PM (UTC)