Prowler: legacy gcp auth-provider in kubeconfig runs commands on the shared scan worker

Impact

Prowler's kubeconfig validator rejected exec blocks but not the legacy gcp auth-provider with cmd-path and cmd-args, so POST /api/v1/providers/{id}/connection loads attacker-supplied kubeconfig content and the Kubernetes client runs that command through subprocess.Popen on the shared worker. Any low-privilege tenant of a Prowler deployment therefore gets code execution on the worker that scans every other tenant's environment - and that worker holds or can reach the cloud and cluster credentials for all of them. For an operator running Prowler over their Kubernetes GPU clusters, the compromise is not of the scanner but of the credential set the scanner uses, which typically includes broad read access across the fleet.

Who can reach it

Network access to the Prowler API with any authenticated low-privilege account able to add a provider and run a connection test. Execution lands on the shared Celery-style worker, not on the caller's own infrastructure.

What to do

Upgrade to Prowler 5.36.0 and restart the API and worker processes (fix in commit 0b782fc extends the validator to cover the legacy auth-provider path). No configuration workaround is published; restricting who may add Kubernetes providers narrows the caller pool but does not close it. This is a container/daemon restart of the Prowler stack, not a fleet action. On a multi-tenant deployment, rotate the cloud and cluster credentials the workers hold.

References

Related entries

• lldpd (lldp_decode, management addresses): Buffer overflow in lldpd's LLDP decoder via large management addressesCVE-2015-8011 · lldpd (lldp_decode, management addresses)Critical
• Lantronix xPrintServer: The device ships with a hardcoded root account baked into every unit of a given firmware lineCVE-2016-4325 · Lantronix xPrintServerCritical
• HPE iLO3 / iLO4: Multiple unspecified flaws allowing remote information disclosure, data modification and DoSCVE-2016-4375 · HPE iLO3 / iLO4Critical
• Tridium Niagara AX (<=3.8) and Niagara 4 (<=4.4) framework: Log into the Niagara platform with a disabled account nameCVE-2017-16748 · Tridium Niagara AX (<=3.8) and Niagara 4 (<=4.4) frameworkCritical
• Lenovo / IBM Integrated Management Module 2 (IMM2) web administration service: The overflow is inside theCVE-2017-3774 · Lenovo / IBM Integrated Management Module 2 (IMM2) web administration serviceCritical
• Intel Active Management Technology / Standard Manageability: An authentication bypass in the AMT web interface: sendingCVE-2017-5689 · Intel Active Management Technology / Standard ManageabilityCritical