Поиск уязвимостей
Количество 9
Количество 9
BDU:2026-01021
Уязвимость библиотеки клиентских инструментов для платформы мониторинга sentry-sdk, позволяющая нарушителю получить несанкционированный доступ к защищаемой информации
CVE-2024-40647
sentry-sdk is the official Python SDK for Sentry.io. A bug in Sentry's Python SDK < 2.8.0 allows the environment variables to be passed to subprocesses despite the `env={}` setting. In Python's `subprocess` calls, all environment variables are passed to subprocesses by default. However, if you specifically do not want them to be passed to subprocesses, you may use `env` argument in `subprocess` calls. Due to the bug in Sentry SDK, with the Stdlib integration enabled (which is enabled by default), this expectation is not fulfilled, and all environment variables are being passed to subprocesses instead. The issue has been patched in pull request #3251 and is included in sentry-sdk==2.8.0. We strongly recommend upgrading to the latest SDK version. However, if it's not possible, and if passing environment variables to child processes poses a security risk for you, you can disable all default integrations.
CVE-2024-40647
sentry-sdk is the official Python SDK for Sentry.io. A bug in Sentry's Python SDK < 2.8.0 allows the environment variables to be passed to subprocesses despite the `env={}` setting. In Python's `subprocess` calls, all environment variables are passed to subprocesses by default. However, if you specifically do not want them to be passed to subprocesses, you may use `env` argument in `subprocess` calls. Due to the bug in Sentry SDK, with the Stdlib integration enabled (which is enabled by default), this expectation is not fulfilled, and all environment variables are being passed to subprocesses instead. The issue has been patched in pull request #3251 and is included in sentry-sdk==2.8.0. We strongly recommend upgrading to the latest SDK version. However, if it's not possible, and if passing environment variables to child processes poses a security risk for you, you can disable all default integrations.
CVE-2024-40647
Unintentional exposure of environment variables to subprocesses in sentry-sdk
CVE-2024-40647
sentry-sdk is the official Python SDK for Sentry.io. A bug in Sentry's ...
openSUSE-SU-2024:0214-1
Security update for python-sentry-sdk
ROS-20260122-80-0001
Уязвимость python-sentry-sdk
ROS-20260122-73-0001
Уязвимость python-sentry-sdk
GHSA-g92j-qhmh-64v2
Sentry's Python SDK unintentionally exposes environment variables to subprocesses
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
 | BDU:2026-01021 Уязвимость библиотеки клиентских инструментов для платформы мониторинга sentry-sdk, позволяющая нарушителю получить несанкционированный доступ к защищаемой информации | CVSS3: 5.3 | 0% Низкий | больше 2 лет назад |
 | CVE-2024-40647 sentry-sdk is the official Python SDK for Sentry.io. A bug in Sentry's Python SDK < 2.8.0 allows the environment variables to be passed to subprocesses despite the `env={}` setting. In Python's `subprocess` calls, all environment variables are passed to subprocesses by default. However, if you specifically do not want them to be passed to subprocesses, you may use `env` argument in `subprocess` calls. Due to the bug in Sentry SDK, with the Stdlib integration enabled (which is enabled by default), this expectation is not fulfilled, and all environment variables are being passed to subprocesses instead. The issue has been patched in pull request #3251 and is included in sentry-sdk==2.8.0. We strongly recommend upgrading to the latest SDK version. However, if it's not possible, and if passing environment variables to child processes poses a security risk for you, you can disable all default integrations. | CVSS3: 5.3 | 0% Низкий | больше 2 лет назад |
 | CVE-2024-40647 sentry-sdk is the official Python SDK for Sentry.io. A bug in Sentry's Python SDK < 2.8.0 allows the environment variables to be passed to subprocesses despite the `env={}` setting. In Python's `subprocess` calls, all environment variables are passed to subprocesses by default. However, if you specifically do not want them to be passed to subprocesses, you may use `env` argument in `subprocess` calls. Due to the bug in Sentry SDK, with the Stdlib integration enabled (which is enabled by default), this expectation is not fulfilled, and all environment variables are being passed to subprocesses instead. The issue has been patched in pull request #3251 and is included in sentry-sdk==2.8.0. We strongly recommend upgrading to the latest SDK version. However, if it's not possible, and if passing environment variables to child processes poses a security risk for you, you can disable all default integrations. | CVSS3: 5.3 | 0% Низкий | больше 2 лет назад |
 | CVE-2024-40647 Unintentional exposure of environment variables to subprocesses in sentry-sdk | 0% Низкий | около 1 года назад | |
| CVE-2024-40647 sentry-sdk is the official Python SDK for Sentry.io. A bug in Sentry's ... | CVSS3: 5.3 | 0% Низкий | больше 2 лет назад |
 | openSUSE-SU-2024:0214-1 Security update for python-sentry-sdk | 0% Низкий | больше 2 лет назад | |
 | ROS-20260122-80-0001 Уязвимость python-sentry-sdk | CVSS3: 5.3 | 0% Низкий | 10 месяцев назад |
| ROS-20260122-73-0001 Уязвимость python-sentry-sdk | CVSS3: 5.3 | 0% Низкий | 10 месяцев назад |
| GHSA-g92j-qhmh-64v2 Sentry's Python SDK unintentionally exposes environment variables to subprocesses | CVSS3: 2.5 | 0% Низкий | больше 2 лет назад |
Уязвимостей на страницу