🚨 [security] Update all of sentry 8.4.0 → 9.14.0 (major)

[depfu]

---

🚨 Your current dependencies have known security vulnerabilities 🚨

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!

---

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ @​sentry/browser (8.4.0 → 9.14.0) · Repo · Changelog

Security Advisories 🚨

🚨 Sentry SDK Prototype Pollution gadget in JavaScript SDKs

Impact

In case a Prototype Pollution vulnerability is present in a user's application or bundled libraries, the Sentry SDK could potentially serve as a gadget to exploit that vulnerability. The exploitability depends on the specific details of the underlying Prototype Pollution issue.

Note

This advisory does not indicate the presence of a Prototype Pollution within the Sentry SDK itself. Users are strongly advised to first address any Prototype Pollution vulnerabilities in their application, as they pose a more critical security risk.

Patches

The issue was patched in all Sentry JavaScript SDKs starting from the 8.33.0 version.
Also, the fix was backported to SDK v7 in 7.119.1.

References

• Prototype Pollution
• Prototype Pollution gadgets
• sentry-javascript#13838

Release Notes

Too many releases to show here. View the full release notes.

Commits

See the full diff on Github. The new version differs by 20 commits:

• release: 9.14.0
• Merge pull request #16115 from getsentry/prepare-release/9.14.0
• rm ref pr
• meta(changelog): Update changelog for 9.14.0
• feat(nestjs): Gracefully handle RPC scenarios in `SentryGlobalFilter` (#16066)
• feat(nextjs): Improve server component data (#15996)
• ref(core): Remove internal `utils-hoist` re-export (#16114)
• fix(node): Make body capturing more robust (#16105)
• feat(deps): Bump @prisma/instrumentation from 6.5.0 to 6.6.0 (#16102)
• build(deps): Bump fastify from 5.0.0 to 5.3.2 in /dev-packages/e2e-tests/test-applications/node-fastify-5 (#16097)
• ref(node): Log when incoming request bodies are being captured (#16104)
• feat(react-router): Trace propagation (#16070)
• feat(nuxt): Log when adding HTML trace meta tags (#16044)
• feat: Add Supabase Integration (#15719)
• test(nuxt): Add tests for trace baggage (#16046)
• build(deps): Bump astro from 4.16.1 to 4.16.18 in /dev-packages/e2e-tests/test-applications/cloudflare-astro (#16087)
• ci: Fix additional label (#16085)
• Merge pull request #16083 from getsentry/master
• ci: Finally fix it for real real (#16082)
• Merge branch 'release/9.13.0'

✳️ @​sentry/node (8.4.0 → 9.14.0) · Repo · Changelog

Security Advisories 🚨

🚨 Potential DoS when using ContextLines integration

Impact

The ContextLines integration uses readable streams to more efficiently use memory when reading files. The ContextLines integration is used to attach source context to outgoing events.

The stream was not explicitly closed after use. This could lead to excessive amounts of file handles open on the system and potentially lead to a Denial of Service (DoS).

The ContextLines integration is enabled by default in the Node SDK (@sentry/node) and SDKs that run in Node.js environments (@sentry/astro, @sentry/aws-serverless, @sentry/bun, @sentry/google-cloud-serverless, @sentry/nestjs, @sentry/nextjs, @sentry/nuxt, @sentry/remix, @sentry/solidstart, @sentry/sveltekit).

Patches

Users should upgrade to version 8.49.0 or higher.

Workarounds

To remediate this issue in affected versions without upgrading to version 8.49.0 and above you can disable the ContextLines integration. See the docs for more details.

Sentry.init({
  // ...
  integrations: function (integrations) {
    // integrations will be all default integrations
    return integrations.filter(function (integration) {
      return integration.name !== "ContextLines";
    });
  },
});

If you disable the ContextLines integration, you will lose source context on your error events.

References

• Reported issue: #14892
• PR Fix: #14997

Release Notes

Too many releases to show here. View the full release notes.

Commits

See the full diff on Github. The new version differs by 20 commits:

• release: 9.14.0
• Merge pull request #16115 from getsentry/prepare-release/9.14.0
• rm ref pr
• meta(changelog): Update changelog for 9.14.0
• feat(nestjs): Gracefully handle RPC scenarios in `SentryGlobalFilter` (#16066)
• feat(nextjs): Improve server component data (#15996)
• ref(core): Remove internal `utils-hoist` re-export (#16114)
• fix(node): Make body capturing more robust (#16105)
• feat(deps): Bump @prisma/instrumentation from 6.5.0 to 6.6.0 (#16102)
• build(deps): Bump fastify from 5.0.0 to 5.3.2 in /dev-packages/e2e-tests/test-applications/node-fastify-5 (#16097)
• ref(node): Log when incoming request bodies are being captured (#16104)
• feat(react-router): Trace propagation (#16070)
• feat(nuxt): Log when adding HTML trace meta tags (#16044)
• feat: Add Supabase Integration (#15719)
• test(nuxt): Add tests for trace baggage (#16046)
• build(deps): Bump astro from 4.16.1 to 4.16.18 in /dev-packages/e2e-tests/test-applications/cloudflare-astro (#16087)
• ci: Fix additional label (#16085)
• Merge pull request #16083 from getsentry/master
• ci: Finally fix it for real real (#16082)
• Merge branch 'release/9.13.0'

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[depfu]

Closed in favor of #554.

[depfu]

Closed in favor of #554.