CVE-2023-46729

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

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

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.

Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside. Typical impact: access to internal metadata services, internal APIs, or cloud credentials.

CVE-2023-46729 has a CVSS score of 6.1 (Medium). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (7.77.0); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

The problem has been fixed in sentry/[email protected]

1. What is CVE-2023-46729? CVE-2023-46729 is a medium-severity server-side request forgery (SSRF) vulnerability in @sentry/nextjs (npm), affecting versions >= 7.26.0, < 7.77.0. It is fixed in 7.77.0. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.
2. How severe is CVE-2023-46729? CVE-2023-46729 has a CVSS score of 6.1 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of @sentry/nextjs are affected by CVE-2023-46729? @sentry/nextjs (npm) versions >= 7.26.0, < 7.77.0 is affected.
4. Is there a fix for CVE-2023-46729? Yes. CVE-2023-46729 is fixed in 7.77.0. Upgrade to this version or later.
5. Is CVE-2023-46729 exploitable, and should I be worried? Whether CVE-2023-46729 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2023-46729 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2023-46729? Upgrade @sentry/nextjs to 7.77.0 or later.

Other vulnerabilities in @sentry/nextjs