OpsTree BuildPiper before 2.7.0 Broken Access Control via git_repo API
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| OpsTree Solutions | BuildPiper | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Opstree Solutions | Buildpiper |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.359% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Opstree Solutions
Opstree Solutions buildpiper |
|
| Vendors & Products |
Opstree Solutions
Opstree Solutions buildpiper |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | OpsTree BuildPiper before 2.7.0 contains a broken access control vulnerability that allows authenticated users to list and build from Git repositories restricted to other projects. Attackers can enumerate repositories via GET /api/v1/git_repo/?all=true and submit any git_repo_id to the ci endpoint, cloning other projects' source code, manifests, and committed secrets. | |
| Title | OpsTree BuildPiper before 2.7.0 Broken Access Control via git_repo API | |
| Weaknesses | CWE-639 | |
| References |
| |
| Metrics |
cvssV3_1
|