Skip to content
Fencer Intel
low 3.7

GHSA-r5w7-f542-q2j4 json

Potential DoS when using ContextLines integration

published last yr. modified last yr.

cvss
3.7
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

### Impact The [ContextLines integration](https://docs.sentry.io/platforms/javascript/guides/node/configuration/integrations/contextlines/) 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](https://docs.sentry.io/platforms/javascript/guides/node/configuration/integrations/#removing-a-default-integration) for more details.

```js 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: https://github.com/getsentry/sentry-javascript/issues/14892 - PR Fix: https://github.com/getsentry/sentry-javascript/pull/14997

Patch / fix

  • npm @sentry/node 8.49.0
  • npm @sentry/astro 8.49.0
  • npm @sentry/aws-serverless 8.49.0
  • npm @sentry/bun 8.49.0
  • npm @sentry/google-cloud-serverless 8.49.0
  • npm @sentry/nestjs 8.49.0
  • npm @sentry/nextjs 8.49.0
  • npm @sentry/nuxt 8.49.0
  • npm @sentry/remix 8.49.0
  • npm @sentry/solidstart 8.49.0
  • npm @sentry/sveltekit 8.49.0

Is GHSA-r5w7-f542-q2j4 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by version score vector
GitHub 3.1 3.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L

Affected packages

ecosystem package affected fixed in
npm @sentry/node
>=8.10.0, <8.49.0
8.49.0
npm @sentry/astro
>=8.10.0, <8.49.0
8.49.0
npm @sentry/aws-serverless
>=8.10.0, <8.49.0
8.49.0
npm @sentry/bun
>=8.10.0, <8.49.0
8.49.0
npm @sentry/google-cloud-serverless
>=8.10.0, <8.49.0
8.49.0
npm @sentry/nestjs
>=8.10.0, <8.49.0
8.49.0
npm @sentry/nextjs
>=8.10.0, <8.49.0
8.49.0
npm @sentry/nuxt
>=8.10.0, <8.49.0
8.49.0
npm @sentry/remix
>=8.10.0, <8.49.0
8.49.0
npm @sentry/solidstart
>=8.10.0, <8.49.0
8.49.0
npm @sentry/sveltekit
>=8.10.0, <8.49.0
8.49.0

Classification

Weakness
  • CWE-774 Allocation of File Descriptors or Handles Without Limits or Throttling

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of getsentry/sentry-javascript published their own advisory on GitHub. Reviewed sources take precedence over it.