Skip to content

Sentry Next.js vulnerable to SSRF via Next.js SDK tunnel endpoint

Moderate severity GitHub Reviewed Published Nov 9, 2023 in getsentry/sentry-javascript • Updated Nov 17, 2023

Package

npm @sentry/nextjs (npm)

Affected versions

>= 7.26.0, < 7.77.0

Patched versions

7.77.0

Description

Impact

An unsanitized input of Next.js SDK tunnel endpoint allows sending HTTP requests to arbitrary URLs and reflecting the response back to the user. This could open door for other attack vectors:

  • client-side vulnerabilities: XSS/CSRF in the context of the trusted domain;
  • interaction with internal network;
  • read cloud metadata endpoints (AWS, Azure, Google Cloud, etc.);
  • local/remote port scan.

This issue only affects users who have Next.js SDK tunneling feature enabled.

Patches

The problem has been fixed in sentry/nextjs@7.77.0

Workarounds

Disable tunneling by removing the tunnelRoute option from Sentry Next.js SDK config — next.config.js or next.config.mjs.

References

Credits

References

@alek-sentry alek-sentry published to getsentry/sentry-javascript Nov 9, 2023
Published to the GitHub Advisory Database Nov 9, 2023
Reviewed Nov 9, 2023
Published by the National Vulnerability Database Nov 10, 2023
Last updated Nov 17, 2023

Severity

Moderate

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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:R/S:C/C:L/I:L/A:N

EPSS score

0.056%
(25th percentile)

Weaknesses

CVE ID

CVE-2023-46729

GHSA ID

GHSA-2rmr-xw8m-22q9

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.