Vulnerabilities (CVE)

Filtered by vendor Woodpecker-ci Subscribe
Filtered by product Woodpecker
Total 4 CVE
CVE Vendors Products Updated CVSS v2 CVSS v3
CVE-2024-41121 1 Woodpecker-ci 1 Woodpecker 2024-10-03 N/A 8.8 HIGH
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.
CVE-2024-41122 1 Woodpecker-ci 1 Woodpecker 2024-10-03 N/A 8.8 HIGH
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.
CVE-2023-40034 1 Woodpecker-ci 1 Woodpecker 2024-02-28 N/A 8.1 HIGH
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.
CVE-2022-29947 1 Woodpecker-ci 1 Woodpecker 2024-02-28 4.3 MEDIUM 6.1 MEDIUM
Woodpecker before 0.15.1 allows XSS via build logs because web/src/components/repo/build/BuildLog.vue lacks escaping.