Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
3 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
GitLab allows sharing a project with another group. Jenkins GitLab Branch Source Plugin 684.veafa7c1e2fe3 and earlier unconditionally discovers projects that are shared with the configured owner group. This allows attackers to configure and share a project, resulting in a crafted Pipeline being built by Jenkins after the next scan of the group’s projects. In GitLab Branch Source Plugin 688.v5fa356ee8520, the default strategy for discovering projects does not discover projects shared with the configured owner group. To discover projects shared with the configured owner group, use the new trait "Discover shared projects".
Recommended action: Upgrade to 688.v5fa or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Jenkins GitLab Branch Source Plugin 684.veafa7c1e2fe3 and earlier does not use a constant-time comparison function when checking whether the provided and expected webhook token are equal. This could potentially allow attackers to use statistical methods to obtain a valid webhook token. GitLab Branch Source Plugin 688.v5fa356ee8520 uses a constant-time comparison function when validating the webhook token.
Recommended action: Upgrade to 688.v5fa or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Jenkins GitLab Branch Source Plugin 684.veafa7c1e2fe3 and earlier does not require POST requests for a form validation endpoint, resulting in a cross-site request forgery (CSRF) vulnerability. This vulnerability allows attackers to connect to an attacker-specified URL. GitLab Branch Source Plugin 688.v5fa356ee8520 requires POST requests for the affected form validation endpoint.
Recommended action: Upgrade to 688.v5fa or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.