@sentry/node, @sentry/astro: Potential DoS when using ContextLines integration
It touches something Phylax follows. No evidence of use yet.
Does it affect what I run?
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- @sentry/node (npm): from 8.10.0, before 8.49.0
- @sentry/astro (npm): from 8.10.0, before 8.49.0
- @sentry/aws-serverless (npm): from 8.10.0, before 8.49.0
- @sentry/bun (npm): from 8.10.0, before 8.49.0
- @sentry/google-cloud-serverless (npm): from 8.10.0, before 8.49.0
- @sentry/nestjs (npm): from 8.10.0, before 8.49.0
- @sentry/nextjs (npm): from 8.10.0, before 8.49.0
- @sentry/nuxt (npm): from 8.10.0, before 8.49.0
- @sentry/remix (npm): from 8.10.0, before 8.49.0
- @sentry/solidstart (npm): from 8.10.0, before 8.49.0
- @sentry/sveltekit (npm): from 8.10.0, before 8.49.0
The fix
@sentry/node (npm) fixed in 8.49.0
npmnpm install "@sentry/node@8.49.0"pnpmpnpm add "@sentry/node@8.49.0"yarnyarn add "@sentry/node@8.49.0"bunbun add "@sentry/node@8.49.0"Check what is installednpm ls @sentry/nodePaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency @sentry/node to 8.49.0 or the nearest later release, to fix GHSA-r5w7-f542-q2j4. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.@sentry/astro (npm) fixed in 8.49.0
npmnpm install "@sentry/astro@8.49.0"pnpmpnpm add "@sentry/astro@8.49.0"yarnyarn add "@sentry/astro@8.49.0"bunbun add "@sentry/astro@8.49.0"Check what is installednpm ls @sentry/astroPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency @sentry/astro to 8.49.0 or the nearest later release, to fix GHSA-r5w7-f542-q2j4. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.@sentry/aws-serverless (npm) fixed in 8.49.0
npmnpm install "@sentry/aws-serverless@8.49.0"pnpmpnpm add "@sentry/aws-serverless@8.49.0"yarnyarn add "@sentry/aws-serverless@8.49.0"bunbun add "@sentry/aws-serverless@8.49.0"Check what is installednpm ls @sentry/aws-serverlessPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency @sentry/aws-serverless to 8.49.0 or the nearest later release, to fix GHSA-r5w7-f542-q2j4. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.@sentry/bun (npm) fixed in 8.49.0
npmnpm install "@sentry/bun@8.49.0"pnpmpnpm add "@sentry/bun@8.49.0"yarnyarn add "@sentry/bun@8.49.0"bunbun add "@sentry/bun@8.49.0"Check what is installednpm ls @sentry/bunPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency @sentry/bun to 8.49.0 or the nearest later release, to fix GHSA-r5w7-f542-q2j4. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.@sentry/google-cloud-serverless (npm) fixed in 8.49.0
npmnpm install "@sentry/google-cloud-serverless@8.49.0"pnpmpnpm add "@sentry/google-cloud-serverless@8.49.0"yarnyarn add "@sentry/google-cloud-serverless@8.49.0"bunbun add "@sentry/google-cloud-serverless@8.49.0"Check what is installednpm ls @sentry/google-cloud-serverlessPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency @sentry/google-cloud-serverless to 8.49.0 or the nearest later release, to fix GHSA-r5w7-f542-q2j4. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.@sentry/nestjs (npm) fixed in 8.49.0
npmnpm install "@sentry/nestjs@8.49.0"pnpmpnpm add "@sentry/nestjs@8.49.0"yarnyarn add "@sentry/nestjs@8.49.0"bunbun add "@sentry/nestjs@8.49.0"Check what is installednpm ls @sentry/nestjsPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency @sentry/nestjs to 8.49.0 or the nearest later release, to fix GHSA-r5w7-f542-q2j4. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.@sentry/nextjs (npm) fixed in 8.49.0
npmnpm install "@sentry/nextjs@8.49.0"pnpmpnpm add "@sentry/nextjs@8.49.0"yarnyarn add "@sentry/nextjs@8.49.0"bunbun add "@sentry/nextjs@8.49.0"Check what is installednpm ls @sentry/nextjsPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency @sentry/nextjs to 8.49.0 or the nearest later release, to fix GHSA-r5w7-f542-q2j4. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.@sentry/nuxt (npm) fixed in 8.49.0
npmnpm install "@sentry/nuxt@8.49.0"pnpmpnpm add "@sentry/nuxt@8.49.0"yarnyarn add "@sentry/nuxt@8.49.0"bunbun add "@sentry/nuxt@8.49.0"Check what is installednpm ls @sentry/nuxtPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency @sentry/nuxt to 8.49.0 or the nearest later release, to fix GHSA-r5w7-f542-q2j4. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.@sentry/remix (npm) fixed in 8.49.0
npmnpm install "@sentry/remix@8.49.0"pnpmpnpm add "@sentry/remix@8.49.0"yarnyarn add "@sentry/remix@8.49.0"bunbun add "@sentry/remix@8.49.0"Check what is installednpm ls @sentry/remixPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency @sentry/remix to 8.49.0 or the nearest later release, to fix GHSA-r5w7-f542-q2j4. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.@sentry/solidstart (npm) fixed in 8.49.0
npmnpm install "@sentry/solidstart@8.49.0"pnpmpnpm add "@sentry/solidstart@8.49.0"yarnyarn add "@sentry/solidstart@8.49.0"bunbun add "@sentry/solidstart@8.49.0"Check what is installednpm ls @sentry/solidstartPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency @sentry/solidstart to 8.49.0 or the nearest later release, to fix GHSA-r5w7-f542-q2j4. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.@sentry/sveltekit (npm) fixed in 8.49.0
npmnpm install "@sentry/sveltekit@8.49.0"pnpmpnpm add "@sentry/sveltekit@8.49.0"yarnyarn add "@sentry/sveltekit@8.49.0"bunbun add "@sentry/sveltekit@8.49.0"Check what is installednpm ls @sentry/sveltekitPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency @sentry/sveltekit to 8.49.0 or the nearest later release, to fix GHSA-r5w7-f542-q2j4. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
Fix commands generated from the advisory's versions. No model wrote them.
In plain words
Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.
Evidence
No evidence that it is being used, or can be. It is listed because of what it affects.
Timeline
- First published here, as "For your digest".