Sentry-Javascript deals with leaked sensitive headers when `sendDefaultPii` is set to `true`
getsentry sentry-javascript
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| @sentry/node npm |
|
|
| @sentry/astro npm |
|
|
| @sentry/aws-serverless npm |
getsentry sentry-javascript
| Product | Affected | Fixed in |
|---|---|---|
| @sentry/node npm |
|
|
| @sentry/astro npm |
|
|
| @sentry/aws-serverless npm |
≥ 10.11.0 · < 10.27.0
|
| @sentry/bun npm |
|
|
| @sentry/google-cloud-serverless npm |
|
|
| @sentry/nestjs npm |
|
|
| @sentry/nextjs npm |
|
|
| @sentry/node-core npm |
|
|
| @sentry/nuxt npm |
|
|
| @sentry/remix npm |
|
|
| @sentry/solidstart npm |
|
|
| @sentry/sveltekit npm |
|
|
Sentry-Javascript is an official Sentry SDKs for JavaScript. From version 10.11.0 to before 10.27.0, when a Node.js application using the Sentry SDK has sendDefaultPii: true it is possible to inadvertently send certain sensitive HTTP headers, including the Cookie header, to Sentry. Those headers would be stored within a Sentry organization as part of the associated trace. A person with access to the Sentry organization could then view and use these sensitive values to impersonate or escalate their privileges within the application. This issue has been patched in version 10.27.0.
From the CVE record · GitHub_M
Affected Sentry JavaScript SDK packages can send sensitive HTTP headers, including Cookie, to Sentry when a Node.js application sets sendDefaultPii: true. The headers are stored in an organization's traces, where someone with access to that Sentry organization could view and use them to impersonate users or escalate privileges in the application.
Operators of Node.js applications using @sentry/node, @sentry/astro, @sentry/aws-serverless, @sentry/bun, @sentry/google-cloud-serverless, @sentry/nestjs, @sentry/nextjs, @sentry/node-core, @sentry/nuxt, @sentry/remix, @sentry/solidstart, or @sentry/sveltekit at versions >=10.11.0 and <10.27.0 should check their deployments.