| Package | Affected versions | Patched versions |
|---|---|---|
| bugsink | < 2.2.0 | 2.2.0 |
Bugsink before 2.2.0 resolved sourcemaps and debug files by debug ID without scoping that lookup to the project that owned the uploaded metadata. An authenticated user with access to one project could cause event processing in that project to use sourcemap/debug-file metadata uploaded for another project in the same Bugsink instance, if the same debug ID was referenced.
This could disclose source context or symbolication-derived context from another project on the same Bugsink instance.
For sourcemaps, the documented upload flow used sentry-cli sourcemaps upload with --project=ignoredfornow. In other words, Bugsink did not historically treat the project value supplied during sourcemap upload as meaningful project ownership. This was documented, but at the same time the sentry-cli, which requires project as a parameter, was the recommended mechanism for uploads. This could reasonably lead people to expect that sourcemaps uploads would respect the provided project-boundary.
For minidumps/debug files specifically, the affected functionality also required FEATURE_MINIDUMPS to be enabled. That feature was marked experimental.
The practical impact is further limited by Bugsink’s deployment model: self-hosted instances are commonly operated within a single organization/trust domain, and Hosted Bugsink uses separate Bugsink instances per tenant. The issue does not cross Hosted Bugsink tenant boundaries.
2.1.3 and earlier are affected.
2.2.0 fixes this issue.
After upgrading, upload sourcemaps/debug files with project information.
To remove legacy projectless sourcemap metadata immediately, run, after upgrading:
bugsink-manage delete_legacy_sourcemaps
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free