Harness through 3.3.0 Missing Access Control via infraproviders endpoint
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.1epss 0.2%
exploitation probability
0.2%top 88% of all CVEs
observed exploitation
nono source reports it
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.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Affected products
harness · harnessReferences
https://github.com/harness/harnesshttps://github.com/harness/harness/blob/v3.3.0/app/api/controller/infraprovider/find.go#L25-L41https://github.com/harness/harness/blob/v3.3.0/app/api/controller/infraprovider/list.go#L37https://github.com/harness/harness/issues/3697https://www.vulncheck.com/advisories/harness-through-3.3.0-missing-access-control-via-infraproviders-endpoint