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. Those who want to handle filtering of these values on the server-side can also use Sentry's advanced data scrubbing feature to account for the custom cookie names. Look for the `$http.cookies`, `$http.headers`, `$request.cookies`, or `$request.headers` fields to target with a scrubbing rule.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - 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. Those     who want to handle filtering of these values on the server-side can also use Sentry's advanced data     scrubbing feature to account for the custom cookie names. Look for the `$http.cookies`, `$http.headers`,     `$request.cookies`, or `$request.headers` fields to target with a scrubbing rule. (CVE-2023-28117)

Note that Nessus relies on the presence of the package as reported by the vendor.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - 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. Those
    who want to handle filtering of these values on the server-side can also use Sentry's advanced data
    scrubbing feature to account for the custom cookie names. Look for the `$http.cookies`, `$http.headers`,
    `$request.cookies`, or `$request.headers` fields to target with a scrubbing rule. (CVE-2023-28117)

The version of FreeBSD installed on the remote host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the 15dae5cc-9ee6-4577-a93e-2ab57780e707 advisory.

  - 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. Those     who want to handle filtering of these values on the server-side can also use Sentry's advanced data     scrubbing feature to account for the custom cookie names. Look for the `$http.cookies`, `$http.headers`,     `$request.cookies`, or `$request.headers` fields to target with a scrubbing rule. (CVE-2023-28117)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Type	Severity
262182	Linux Distros Unpatched Vulnerability : CVE-2023-28117	Nessus	Misc.	Local	medium
408829	SCA: security update for sentry-sdk (GHSA-29pr-6jr8-q5jm)	Tenable Cloud Security	SCA Checks	Local	medium
408829	SCA: security update for sentry-sdk (GHSA-29pr-6jr8-q5jm)	Tenable Self-Hosted Container Security	SCA Checks	Local	medium
174314	FreeBSD : py39-sentry-sdk -- sensitive cookies leak (15dae5cc-9ee6-4577-a93e-2ab57780e707)	Nessus	FreeBSD Local Security Checks	Local	medium

Detections

Analytics

CVE-2023-28117

medium

Tenable Plugins

medium

medium

medium

medium