Backstage: Sensitive information exposure in Scaffolder
- 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 1.49.6, 1.50.5, 1.54.6, 3.3.1, 3.4.1, and 2 more
- 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: total
Summary
Backstage is an open framework for building developer portals. Prior to 3.3.1, 3.4.1, 4.0.3 and 4.1.0, the @backstage/plugin-scaffolder-backend package is affected by sensitive information exposure in scaffolder. An authenticated Backstage user who can read another user's Scaffolder task may receive internal execution data. In deployments where that data contains credentials for an external service, this may permit disclosure and unauthorized changes in that external service. This issue is fixed in versions 3.3.1, 3.4.1, 4.0.3 and 4.1.0.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- backstage backstage
fixed in 1.49.6; From 1.50.0-next.0 · fixed in 1.50.5; From 1.51.0-next.0 · fixed in 1.54.6
- @backstage plugin-scaffolder-backend
fixed in 3.3.1; From 3.4.0 · fixed in 3.4.1; From 4.0.0 · fixed in 4.0.3; From 4.0.4 · fixed in 4.1.0
- @backstage/plugin-scaffolder-backendnpm
fixed in 3.3.1
- @backstage/plugin-scaffolder-backendnpm
From 3.4.0 · fixed in 3.4.1
- @backstage/plugin-scaffolder-backendnpm
From 4.0.0 · fixed in 4.0.3
- @backstage/plugin-scaffolder-backendnpm
From 4.0.4 · fixed in 4.1.0