Woodpecker is a CI/CD engine. From 1.0.0 until 3.16.0, pipeline/backend/kubernetes/backend_options.go defines backend_options.kubernetes.serviceAccountName, and the Kubernetes backend in pipeline/backend/kubernetes/pod.go copies that pipeline-step value directly into the pod specification without administrator authorization. Any user with Push permission on a connected repository can therefore run pipeline pods under an arbitrary ServiceAccount in the pipeline namespace and inherit that account's RBAC permissions.
When a privileged ServiceAccount is reachable, the attacker can exfiltrate secrets such as database credentials, API keys, and TLS certificates and may take over the cluster. This issue is fixed in version 3.16.0.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
Low
Easy to exploit
Attack Requirements
Present
Additional conditions required
Privileges Required
Low
Basic privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
High
Complete data leak
Integrity
High
Complete data modification
Availability
High
Complete denial of service
CVSS Vector v4.0
Weakness Type (CWE)
References 5
https://github.com/woodpecker-ci/woodpecker/commit/5df9d52260626c074c6caafb2dc8…
security-advisories@github.com
https://github.com/woodpecker-ci/woodpecker/commit/609ba481b5e912f59aaae8ca7bc2…
security-advisories@github.com
https://github.com/woodpecker-ci/woodpecker/pull/6792
security-advisories@github.com
https://github.com/woodpecker-ci/woodpecker/releases/tag/v3.16.0
security-advisories@github.com
https://github.com/woodpecker-ci/woodpecker/security/advisories/GHSA-qf34-295c-…
security-advisories@github.com