CVE-2023-46729: Sentry Next.js vulnerable to SSRF via Next.js SDK tunnel endpoint
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 Sentry Next.js tunneling feature The fix More Information
Credits Praveen Kumar
Other sources
sentry-javascript provides Sentry SDKs for JavaScript. 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 issue only affects users who have Next.js SDK tunneling feature enabled. The problem has been fixed in version 7.77.0.
Affected Software
Remediation
Patch Available
Event History
Frequently Asked Questions
What is the impact of CVE-2023-46729?
The vulnerability allows sending HTTP requests to arbitrary URLs and reflecting the response back to the user, which can lead to client-side vulnerabilities like XSS/CSRF.
Which software is affected by CVE-2023-46729?
The vulnerability affects the @sentry/nextjs package with versions between 7.26.0 and 7.77.0.
What is the severity of CVE-2023-46729?
CVE-2023-46729 has a severity rating of 9.3 (Critical).
How can I fix CVE-2023-46729?
To fix CVE-2023-46729, update the @sentry/nextjs package to version 7.77.0 or later.
Where can I find more information about CVE-2023-46729?
Additional information about CVE-2023-46729 can be found in the GitHub advisory and pull request linked in the references section.