Backstage: Catalog unprocessed read endpoints allow authenticated cross-owner data access without permission checks
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 0.6.11, 0.2.30, 0.0.15
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Backstage is an open framework for building developer portals. Prior to 0.6.11, the unprocessed entities read endpoints in @backstage/plugin-catalog-backend-module-unprocessed do not enforce permission authorization checks. Any authenticated user can access unprocessed entity records regardless of ownership. This is an information disclosure vulnerability affecting Backstage installations using this module. This is patched in @backstage/plugin-catalog-backend-module-unprocessed version 0.6.11, @backstage/plugin-catalog-unprocessed-entities-common version 0.0.15 and @backstage/plugin-catalog-unprocessed-entities version 0.2.30.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- @backstage plugin-catalog-backend-module-unprocessed
fixed in 0.6.11
- @backstage plugin-catalog-unprocessed-entities
fixed in 0.2.30
- @backstage plugin-catalog-unprocessed-entities-common
fixed in 0.0.15
- @backstage/plugin-catalog-unprocessed-entities-commonnpm
fixed in 0.0.15
- @backstage/plugin-catalog-unprocessed-entitiesnpm
fixed in 0.2.30
- @backstage/plugin-catalog-backend-module-unprocessednpm
fixed in 0.6.11