The Sentry API incorrectly returns the access-control-allow-credentials: true
HTTP header if the Origin
request header ends with the system.base-hostname
option of Sentry installation. This only affects installations that have system.base-hostname
option explicitly set, as it is empty by default.
Impact is limited since recent versions of major browsers have cross-site cookie blocking enabled by default. However, this flaw could allow other multi-step attacks.
The patch has been released in Sentry 23.6.2.
For Sentry SaaS customers, no action is needed.
For self-hosted Sentry installations that have system.base-hostname
explicitly set, it is recommended to upgrade the installation to 23.6.2 or higher. There are no known workarounds.
{ "nvd_published_at": "2023-07-06T23:15:09Z", "cwe_ids": [ "CWE-697", "CWE-863", "CWE-942" ], "severity": "MODERATE", "github_reviewed": true, "github_reviewed_at": "2023-07-06T22:55:44Z" }