Summary
Woodpecker's custom environment variables allow to alter execution flow of plugins
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
Enable the "gated" repo feature and review each change upfront of running
References
- https://github.com/woodpecker-ci/woodpecker/pull/3909
- https://github.com/woodpecker-ci/woodpecker/pull/3934
- https://github.com/woodpecker-ci/woodpecker-security/issues/10 (info will be published later at https://github.com/woodpecker-ci/woodpecker/issues/3929)
- https://github.com/woodpecker-ci/woodpecker/issues/3929 (info will be published later once we got adoption of the update)
Credits
Impact
The server allow to create any user who can trigger a pipeline run malicious workflows:
- Those workflows can either lead to a host takeover that runs the agent executing the workflow.
- Or allow to extract the secrets who would be normally provided to the plugins who's entrypoint are overwritten.
CVE-2024-41122 has a CVSS score of 7.5 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.7.0); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
https://github.com/woodpecker-ci/woodpecker/pull/3909
https://github.com/woodpecker-ci/woodpecker/pull/3934
Frequently Asked Questions
- What is CVE-2024-41122? CVE-2024-41122 is a medium-severity security vulnerability in go.woodpecker-ci.org/woodpecker/v2 (go), affecting versions < 2.7.0. It is fixed in 2.7.0.
- How severe is CVE-2024-41122? CVE-2024-41122 has a CVSS score of 7.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which packages are affected by CVE-2024-41122?
go.woodpecker-ci.org/woodpecker/v2(go) (versions < 2.7.0)go.woodpecker-ci.org/woodpecker(go) (versions < 2.7.0)
- Is there a fix for CVE-2024-41122? Yes. CVE-2024-41122 is fixed in 2.7.0. Upgrade to this version or later.
- Is CVE-2024-41122 exploitable, and should I be worried? Whether CVE-2024-41122 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2024-41122 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2024-41122?
- Upgrade
go.woodpecker-ci.org/woodpecker/v2to 2.7.0 or later - Upgrade
go.woodpecker-ci.org/woodpeckerto 2.7.0 or later
- Upgrade