CVSS: 9.3EPSS: 0%CPEs: 1EXPL: 0CVE-2023-46729 – Sentry Next.js vulnerable to SSRF via Next.js SDK tunnel endpoint
https://notcve.org/view.php?id=CVE-2023-46729
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. sentry-javascript proporciona SDK de Sentry para JavaScript. Una entrada no sanitizada del endpoint del túnel SDK de Next.js permite enviar solicitudes HTTP a URL arbitrarias y reflejar la respuesta al usuario. • https://github.com/getsentry/sentry-javascript/commit/ddbda3c02c35aba8c5235e0cf07fc5bf656f81be https://github.com/getsentry/sentry-javascript/pull/9415 https://github.com/getsentry/sentry-javascript/security/advisories/GHSA-2rmr-xw8m-22q9 • CWE-918: Server-Side Request Forgery (SSRF) •
CVSS: 7.6EPSS: 0%CPEs: 1EXPL: 0CVE-2023-28117 – Sentry SDK leaks sensitive session information when `sendDefaultPII` is set to `True`
https://notcve.org/view.php?id=CVE-2023-28117
Sentry SDK is the official Python SDK for Sentry, real-time crash reporting software. When using the Django integration of versions prior to 1.14.0 of the Sentry SDK in a specific configuration it is possible to leak sensitive cookies values, including the session cookie to Sentry. These sensitive cookies could then be used by someone with access to your Sentry issues to impersonate or escalate their privileges within your application. In order for these sensitive values to be leaked, the Sentry SDK configuration must have `sendDefaultPII` set to `True`; one must use a custom name for either `SESSION_COOKIE_NAME` or `CSRF_COOKIE_NAME` in one's Django settings; and one must not be configured in one's organization or project settings to use Sentry's data scrubbing features to account for the custom cookie names. As of version 1.14.0, the Django integration of the `sentry-sdk` will detect the custom cookie names based on one's Django settings and will remove the values from the payload before sending the data to Sentry. As a workaround, use the SDK's filtering mechanism to remove the cookies from the payload that is sent to Sentry. For error events, this can be done with the `before_send` callback method and for performance related events (transactions) one can use the `before_send_transaction` callback method. • https://github.com/getsentry/sentry-python/pull/1842 https://github.com/getsentry/sentry-python/releases/tag/1.14.0 https://github.com/getsentry/sentry-python/security/advisories/GHSA-29pr-6jr8-q5jm • CWE-201: Insertion of Sensitive Information Into Sent Data CWE-209: Generation of Error Message Containing Sensitive Information •