You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Symbolicator is a service used in Sentry. An attacker could make Symbolicator send GET HTTP requests to arbitrary URLs with internal IP addresses by using a specially crafted HTTP endpoint. The responses of those requests could be exposed via Symbolicator's API.
Impact
In affected Sentry instances, the data could be exposed through the Sentry API and user interface if the attacker has a registered account.
Patches
The issue has been fixed in Symbolicator release 23.11.2, Sentry self-hosted release 23.11.2, and has already been mitigated on sentry.io on November 27.
Workarounds
Please update Symbolicator and Sentry self-hosted. If updating is not possible, the following can be done to mitigate the issue:
Disable JS processing by toggling the option "Allow JavaScript Source Fetching" in Organization Settings > Security & Privacy.
Disable all untrusted public repositories under Project Settings > Debug Files.
Alternatively, if JavaScript and native symbolication are not required, disable Symbolicator completely in config.yml by specifying:
Package and Versions
Package: symbolicator Rust
Affected Version(s): >=0.3.3,<23.11.2
Patched Version(s): 23.11.2
Description
Symbolicator is a service used in Sentry. An attacker could make Symbolicator send GET HTTP requests to arbitrary URLs with internal IP addresses by using a specially crafted HTTP endpoint. The responses of those requests could be exposed via Symbolicator's API.
Impact
In affected Sentry instances, the data could be exposed through the Sentry API and user interface if the attacker has a registered account.
Patches
The issue has been fixed in Symbolicator release 23.11.2, Sentry self-hosted release 23.11.2, and has already been mitigated on sentry.io on November 27.
Workarounds
Please update Symbolicator and Sentry self-hosted. If updating is not possible, the following can be done to mitigate the issue:
Disable JS processing by toggling the option "Allow JavaScript Source Fetching" in Organization Settings > Security & Privacy.
Disable all untrusted public repositories under Project Settings > Debug Files.
Alternatively, if JavaScript and native symbolication are not required, disable Symbolicator completely in config.yml by specifying:
symbolicator.enabled: false
CVSS 3.1 Score and Vector
Example:
CVSS Score: 4.3
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Information
Reference: getsentry/symbolicator#1332
Credit: https://github.com/oioki
The text was updated successfully, but these errors were encountered: