@backstage/integration: Potential reading of SCM URLs using built in token
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 |
|
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Backstage | Backstage |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-95v5-prp4-5gv5 | Backstage vulnerable to potential reading of SCM URLs using built in token |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.396% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Linuxfoundation backstage\/integration
|
|
| CPEs | cpe:2.3:a:linuxfoundation:backstage\/integration:*:*:*:*:*:node.js:*:* | |
| Vendors & Products |
Linuxfoundation \@backstage\/integration
|
Linuxfoundation backstage\/integration
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Linuxfoundation
Linuxfoundation \@backstage\/integration |
|
| CPEs | cpe:2.3:a:linuxfoundation:\@backstage\/integration:*:*:*:*:*:node.js:*:* | |
| Vendors & Products |
Linuxfoundation
Linuxfoundation \@backstage\/integration |
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Backstage
Backstage backstage |
|
| Vendors & Products |
Backstage
Backstage backstage |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Backstage is an open framework for building developer portals. Prior to version 1.20.1, a vulnerability in the SCM URL parsing used by Backstage integrations allowed path traversal sequences in encoded form to be included in file paths. When these URLs were processed by integration functions that construct API URLs, the traversal segments could redirect requests to unintended SCM provider API endpoints using the configured server-side integration credentials. This issue has been patched in version 1.20.1. | |
| Title | @backstage/integration: Potential reading of SCM URLs using built in token | |
| Weaknesses | CWE-22 | |
| References |
| |
| Metrics |
cvssV3_1
|