Custom environment variables allow to alter execution flow of plugins in Woodpecker
woodpecker-ci woodpecker
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| go.woodpecker-ci.org/woodpecker/v2 Go |
|
|
| go.woodpecker-ci.org/woodpecker Go |
|
|
woodpecker-ci woodpecker
| Product | Affected | Fixed in |
|---|---|---|
| go.woodpecker-ci.org/woodpecker/v2 Go |
|
|
| go.woodpecker-ci.org/woodpecker Go |
|
|
Woodpecker is a simple yet powerful CI/CD engine with great extensibility. The server allow to create any user who can trigger a pipeline run malicious workflows: 1. Those workflows can either lead to a host takeover that runs the agent executing the workflow. 2. Or allow to extract the secrets who would be normally provided to the plugins who's entrypoint are overwritten. This issue has been addressed in release version 2.7.0. Users are advised to upgrade. There are no known workarounds for this vulnerability.
From the CVE record · GitHub_M
The Woodpecker server allows a user who can trigger a pipeline run to create malicious workflows. These workflows can take over the host running the agent or extract secrets normally provided to plugins whose entrypoints are overwritten. The attacker needs permission to trigger a pipeline run; no other user interaction is described.
Teams running Woodpecker or the Go packages go.woodpecker-ci.org/woodpecker/v2 and go.woodpecker-ci.org/woodpecker before version 2.7.0 should check their installations.