Skip to content

Woodpecker does not validate webhook before changing any data

High severity GitHub Reviewed Published Aug 16, 2023 in woodpecker-ci/woodpecker • Updated Nov 11, 2023

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 which leads to an update of the repository data that can e.g. allow the takeover of a repository.
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

@6543 6543 published to woodpecker-ci/woodpecker Aug 16, 2023
Published to the GitHub Advisory Database Aug 16, 2023
Reviewed Aug 16, 2023
Published by the National Vulnerability Database Aug 16, 2023
Last updated Nov 11, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.131%
(49th percentile)

Weaknesses

CVE ID

CVE-2023-40034

GHSA ID

GHSA-4gcf-5m39-98mc

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.