Headline
GHSA-4gcf-5m39-98mc: Woodpecker does not validate webhook before changing any data
Impact
An attacker can post malformed webhook data witch lead to an update of the repository data that can e.g. allow the takeover of an repo. This is only critical if the CI is configured for public usage and connected to a forge witch is also in public usage.
Patches
Please use either next or the latest v1.0 e.g. v1.0.2
Workarounds
Secure the CI system by making it inaccessible to untrusted entities, for example, by placing it behind a firewall.
References
Fix: https://github.com/woodpecker-ci/woodpecker/pull/2221 Backport: https://github.com/woodpecker-ci/woodpecker/pull/2222
Package
gomod github.com/woodpecker-ci/woodpecker (Go)
Affected versions
>= 1.0.0, < 1.0.2
Patched versions
1.0.2
Description
Impact
An attacker can post malformed webhook data witch lead to an update of the repository data that can e.g. allow the takeover of an repo.
This is only critical if the CI is configured for public usage and connected to a forge witch is also in public usage.
Patches
Please use either next or the latest v1.0 e.g. v1.0.2
Workarounds
Secure the CI system by making it inaccessible to untrusted entities, for example, by placing it behind a firewall.
References
Fix: woodpecker-ci/woodpecker#2221
Backport: woodpecker-ci/woodpecker#2222
References
- GHSA-4gcf-5m39-98mc
- woodpecker-ci/woodpecker#2221
- woodpecker-ci/woodpecker#2222
- https://github.com/woodpecker-ci/woodpecker/releases/tag/v1.0.2
6543 published to woodpecker-ci/woodpecker
Aug 16, 2023
Published to the GitHub Advisory Database
Aug 16, 2023
Reviewed
Aug 16, 2023
Last updated
Aug 16, 2023
Related news
Woodpecker is a community fork of the Drone CI system. In affected versions an attacker can post malformed webhook data witch lead to an update of the repository data that can e.g. allow the takeover of an repo. This is only critical if the CI is configured for public usage and connected to a forge witch is also in public usage. This issue has been addressed in version 1.0.2. Users are advised to upgrade. Users unable to upgrade should secure the CI system by making it inaccessible to untrusted entities, for example, by placing it behind a firewall.