Skip to content

Sentry's Astro SDK vulnerable to ReDoS

High severity GitHub Reviewed Published Dec 18, 2023 in getsentry/sentry-javascript • Updated Dec 28, 2023

Package

npm @sentry/astro (npm)

Affected versions

>= 7.78.0, < 7.87.0

Patched versions

7.87.0

Description

Impact

A ReDoS (Regular expression Denial of Service) vulnerability has been identified in Sentry's Astro SDK 7.78.0-7.86.0. Under certain conditions, this vulnerability allows an attacker to cause excessive computation times on the server, leading to denial of service (DoS).

Applications that are using Sentry's Astro SDK are affected if:

  1. They're using Sentry instrumentation:
  2. They have configured routes with at least two path params (e.g. /foo/[p1]/bar/[p2]).

Patches

The problem has been patched in @sentry/[email protected].
The corresponding PR: getsentry/sentry-javascript#9815

Workarounds

We strongly recommend upgrading to the latest SDK version. However, if it's not possible, the steps to mitigate the vulnerability without upgrade are:

After these changes, Sentry error reporting will still be functional, but some details such as server-side transactions (and consequently, distributed traces between client and server) will be omitted. We therefore still recommend to update to 7.87.0 as soon as you can.

References

References

@alek-sentry alek-sentry published to getsentry/sentry-javascript Dec 18, 2023
Published to the GitHub Advisory Database Dec 18, 2023
Reviewed Dec 18, 2023
Published by the National Vulnerability Database Dec 20, 2023
Last updated Dec 28, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

0.053%
(22nd percentile)

CVE ID

CVE-2023-50249

GHSA ID

GHSA-x3v3-8xg8-8v72
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.