Backstage: Improper validation of MkDocs plugin configuration in TechDocs
- 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.50.6, 1.54.8, 1.14.7, 1.15.5
- 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. From 0.11.12 until 1.14.7 and 1.15.5, the @backstage/plugin-techdocs-node package is affected by improper validation of mkdocs plugin configuration in techdocs. An authenticated attacker with control over a TechDocs source repository could cause a documentation build to retrieve and publish data from network locations reachable by the build environment. Exposure depends on deployment topology, build mode, and target endpoint protections. Modern cloud metadata services that require tokens or special headers are not directly accessible through the affected behavior. This issue is fixed in @backstage/plugin-techdocs-node versions 1.14.7 and 1.15.5.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- backstage backstage
From 0.71.1 · fixed in 1.50.6; From 1.51.0-next.0 · fixed in 1.54.8
- @backstage plugin-techdocs-node
From 0.11.12 · fixed in 1.14.7; From 1.15.0 · fixed in 1.15.5
- @backstage/plugin-techdocs-nodenpm
From 0.11.12 · fixed in 1.14.7
- @backstage/plugin-techdocs-nodenpm
From 1.15.0 · fixed in 1.15.5