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.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
Low
Easy to exploit
Attack Requirements
None
No additional conditions
Privileges Required
Low
Basic privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
High
Complete data leak
Integrity
None
No data modification
Availability
None
No disruption
CVSS Vector v4.0
Weakness Type (CWE)
Vulnerable Products
harness:harness
References 5
https://github.com/harness/harness
disclosure@vulncheck.com
https://github.com/harness/harness/blob/v3.3.0/app/api/controller/infraprovider…
disclosure@vulncheck.com
https://github.com/harness/harness/blob/v3.3.0/app/api/controller/infraprovider…
disclosure@vulncheck.com
https://github.com/harness/harness/issues/3697
disclosure@vulncheck.com
https://www.vulncheck.com/advisories/harness-through-3.3.0-missing-access-contr…
disclosure@vulncheck.com