sentry-sdk
Affected
- introduced
0, fixed1.14.0(ecosystem)
Fixed versions
1.14.0
Fix
- Fixed version
1.14.0pip install --upgrade sentry-sdk==1.14.0
Advisory
Also known as: CVE-2023-28117, GHSA-29pr-6jr8-q5jm
Sentry SDK leaks sensitive session information when sendDefaultPII is set to True
Impact
When using the Django integration 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.
The below must be true in order for these sensitive values to be leaked:
sendDefaultPII set to TruePatches
As of version 1.14.0, the Django integration of the sentry-sdk will detect the custom cookie names based on your Django settings and will remove the values from the payload _before_ sending the data to Sentry.
Workarounds
If you can not update your sentry-sdk to a patched version than you can use the SDKs 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) you can use the before_send_transaction callback method.
If you'd like to handle filtering of these values on the server-side, you can also use our 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 your scrubbing rule.
References
Credits
High Basis: CVSS v3 score 7.6, vector CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:L/A:N
0, fixed 1.14.0 (ecosystem)1.14.0
1.14.0pip install --upgrade sentry-sdk==1.14.0Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: PyPA Advisory Database · CC BY 4.0