CVE-2023-50249 json
Sentry's Astro SDK vulnerable to ReDoS
published 2023-12-18 2 y ago modified 2026-09-10 1 mo ago also GHSA-x3v3-8xg8-8v72 , EUVD-2023-3320
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 56%
- public exploits
- 0
- none known
Summary
Sentry-Javascript is official Sentry SDKs for JavaScript. 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). This vulnerability has been patched in sentry/astro version 7.87.0.
Patch / fix
- npm @sentry/astro 7.87.0
- sentry astro 7.87.0
Exploit prediction
0.78% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | @sentry/astro | >=7.78.0, <7.87.0 |
7.87.0 |
Affected products
- getsentry sentry-javascript
Classification
References
-
github.com
/getsentry/sentry-javascript/pull/9815
web, patch
-
github.com
/getsentry/sentry-javascript/commit/fe24eb5eefa9d27b14b2b6f9ebd1debca1c208fb
web, patch
-
github.com
/getsentry/sentry-javascript/security/advisories/GHSA-x3v3-8xg8-8v72
web, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2023-50249
advisory
-
docs.sentry.io
/platforms/javascript/guides/astro/manual-setup/#disable-auto-server-instrumentation
web
-
github.com
/getsentry/sentry-javascript
package
-
npmjs.com
/package/@sentry/astro/v/7.87.0
web
Sources
- CVE List CVE-2023-50249
- GitHub Advisory GHSA-x3v3-8xg8-8v72
- NVD CVE-2023-50249
Fencer Vulns 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.