Backstage: Inconsistent repository filtering in Bitbucket Server catalog event updates

[ Description ]Official description

Backstage is an open framework for building developer portals. From 0.4.0 until 0.5.15, the @backstage/plugin-catalog-backend-module-bitbucket-server package is affected by inconsistent repository filtering in bitbucket server catalog event updates. Deployments using event-driven updates in the Bitbucket Server catalog provider may ingest catalog locations from repositories that are excluded by the provider's configured project, repository, or archived-repository filters. An authenticated Bitbucket Server user who can push to a filtered-out repository that remains readable by the configured Backstage integration can trigger a legitimate repository event. The affected event path may then add a Location for that repository even though scheduled discovery excludes it. This issue is fixed in version 0.5.15.

[ Fixes ]Fixes and patches

• @backstage/plugin-catalog-backend-module-bitbucket-server 0.5.15Fixed version · GitHub Advisories · npm package @backstage/plugin-catalog-backend-module-bitbucket-server: upgrade to 0.5.15 or later (affected >= 0.4.0, < 0.5.15)

[ Packages ]Affected open-source packages

• @backstage/plugin-catalog-backend-module-bitbucket-server npmAffected >= 0.4.0, < 0.5.15 · fixed in 0.5.15 · GHSA-c36c-cf6r-ghgj

[ References ]References

• github.com/backstage/backstage/commit/989db63b6f87c8fc04d440f296ad89e10c79b363
• github.com/backstage/backstage/releases/tag/v1.55.0
• github.com/backstage/backstage/security/advisories/GHSA-c36c-cf6r-ghgj