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/[email protected]

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

References

• GHSA-2rmr-xw8m-22q9
• getsentry/sentry-javascript#9415
• getsentry/sentry-javascript@ddbda3c
• https://blog.sentry.io/next-js-sdk-security-advisory-cve-2023-46729/
• https://docs.sentry.io/platforms/javascript/guides/nextjs/manual-setup/#configure-tunneling-to-avoid-ad-blockers
• https://www.npmjs.com/package/@sentry/nextjs/v/7.77.0
• https://nvd.nist.gov/vuln/detail/CVE-2023-46729