Description
Harness through 3.3.0 omits access control validation in the infrastructure provider read endpoint, allowing authenticated users to retrieve provider configurations from spaces they do not belong to. Attackers can query the GET /api/v1/infraproviders endpoint with arbitrary space identifiers to expose sensitive provider metadata including Docker endpoints, TLS certificate paths, and cloud project identifiers.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
harness harness
Default version status: unaffected
0 to ≤ 3.3.0affected
pkg:golang/github.com/harness/gitnessReferences
- https://github.com/harness/harness/issues/3697 ↗
- https://github.com/harness/harness ↗
- https://github.com/harness/harness/blob/v3.3.0/app/api/controller/infraprovider/find.go#L25-L41 ↗
- https://github.com/harness/harness/blob/v3.3.0/app/api/controller/infraprovider/list.go#L37 ↗
- https://www.vulncheck.com/advisories/harness-through-3.3.0-missing-access-control-via-infraproviders-endpoint ↗