Backstage: Improper authorization enforcement for TechDocs static content
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| backstage | backstage | affected |
|
||||||
| @backstage | plugin-techdocs-backend | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Backstage | Backstage |
|
||||||||
| Backstage | Plugin-techdocs-backend |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-rg9r-hr7g-5gc2 | Backstage: Improper authorization enforcement for TechDocs static content |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.289% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Linuxfoundation
Linuxfoundation backstage Linuxfoundation backstage\/plugin-techdocs-backend |
|
| CPEs | cpe:2.3:a:linuxfoundation:backstage:*:*:*:*:*:*:*:* cpe:2.3:a:linuxfoundation:backstage\/plugin-techdocs-backend:*:*:*:*:*:node.js:*:* |
|
| Vendors & Products |
Linuxfoundation
Linuxfoundation backstage Linuxfoundation backstage\/plugin-techdocs-backend |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Backstage
Backstage backstage Backstage plugin-techdocs-backend |
|
| Vendors & Products |
Backstage
Backstage backstage Backstage plugin-techdocs-backend |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-639 | |
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Backstage is an open framework for building developer portals. Prior to 2.2.4, the @backstage/plugin-techdocs-backend package is affected by improper authorization enforcement for techdocs static content. An authenticated user with access to one TechDocs documentation site could craft a URL able to read documentation belonging to a different entity. This only affects deployments using the external TechDocs builder with an external storage provider (S3, GCS, etc.) and the permission framework enabled. Instances that do not use the permission framework are unaffected, since TechDocs content is visible to all authenticated users by design. This issue is fixed in version 2.2.4. | |
| Title | Backstage: Improper authorization enforcement for TechDocs static content | |
| Weaknesses | CWE-22 CWE-862 |
|
| References |
| |
| Metrics |
cvssV3_1
|