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.
Metrics
CVSS 3.1 6.5/10
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NWeakness enumeration
Affected software
Source: the vendor's advisory (CNA). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| harness | harness | <= 3.3.0 |
References
- 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://github.com/harness/harness/issues/3697
- https://www.vulncheck.com/advisories/harness-through-3.3.0-missing-access-control-via-infraproviders-endpoint
Timeline
- Published
- Sep 16, 2026
- Last modified
- Sep 24, 2026
- NVD status
- Awaiting Analysis