sentry_sdk-1.9.5-py2.py3-none-any.whl: 1 vulnerabilities (highest severity is: 6.5)

[mend-bolt-for-github]

Vulnerable Library - sentry_sdk-1.9.5-py2.py3-none-any.whl

Python client for Sentry (https://sentry.io)

Library home page: https://files.pythonhosted.org/packages/7d/c3/7da8ce136e156f07ad75b397bb13a2aebdcc6cc85e0a2a564b79224f94fe/sentry_sdk-1.9.5-py2.py3-none-any.whl

Path to dependency file: /requirements/requirements.txt

Path to vulnerable library: /requirements/requirements.txt

Vulnerabilities

CVE	Severity	CVSS	Dependency	Type	Fixed in (sentry_sdk version)	Remediation Possible**
CVE-2023-28117	Medium	6.5	sentry_sdk-1.9.5-py2.py3-none-any.whl	Direct	sentry-sdk - 1.14.0	❌

**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation

Details

CVE-2023-28117

Vulnerable Library - sentry_sdk-1.9.5-py2.py3-none-any.whl

Python client for Sentry (https://sentry.io)

Library home page: https://files.pythonhosted.org/packages/7d/c3/7da8ce136e156f07ad75b397bb13a2aebdcc6cc85e0a2a564b79224f94fe/sentry_sdk-1.9.5-py2.py3-none-any.whl

Path to dependency file: /requirements/requirements.txt

Path to vulnerable library: /requirements/requirements.txt

Dependency Hierarchy:

• ❌ sentry_sdk-1.9.5-py2.py3-none-any.whl (Vulnerable Library)

Found in base branch: main

Vulnerability Details

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.

Publish Date: 2023-03-22

URL: CVE-2023-28117

CVSS 3 Score Details (6.5)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: Low
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: High
  • Integrity Impact: None
  • Availability Impact: None

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-29pr-6jr8-q5jm

Release Date: 2023-03-22

Fix Resolution: sentry-sdk - 1.14.0

Step up your Open Source Security Game with Mend here