Sentry-Javascript: Middleware Bypass when using Tunnel route
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 9.47.2, 10.75.2, 11.0.0-rc.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: total
Summary
Sentry-Javascript is an official Sentry SDKs for JavaScript. From 9.36.0 until 9.47.2, 10.75.2, and 11.0.0-rc.1, the webpack integration for @sentry/nextjs skips application middleware for every request path under a configured tunnelRoute, while the tunnel rewrite serves only the exact tunnel path with valid o and p query parameters. When an application route directly collides with the tunnel path or a root dynamic segment resolves under it, an unauthenticated request can reach that route without middleware authorization. Exploitation requires tunnelRoute, a webpack build, a colliding route, and middleware being the only authorization control. This issue is fixed in versions 9.47.2, 10.75.2, and 11.0.0-rc.1.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- getsentry sentry-javascript
From 9.36.0 · fixed in 9.47.2; From 10.0.0-alpha.0 · fixed in 10.75.2; From 11.0.0-alpha.0 · fixed in 11.0.0-rc.1
- @sentry/nextjsnpm
From 9.36.0 · fixed in 9.47.2
- @sentry/nextjsnpm
From 10.0.0-alpha.0 · fixed in 10.75.2
- @sentry/nextjsnpm
From 11.0.0-alpha.0 · fixed in 11.0.0-rc.1