Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

Maven package

org.jenkins-ci.plugins:dockerhub-notification

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

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 5.3MavenPublished

    Lack of authentication mechanism for webhook in CloudBees Docker Hub/Registry Notification Plugin

    CVE-2022-45385 · GHSA-v535-pc6r-77qh

    Affected
    • Maven org.jenkins-ci.plugins:dockerhub-notification <= 2.6.2
    Fixed in
    2.6.2.1· Vendor fix available
    Issue
    CloudBees Docker Hub/Registry Notification Plugin provides several webhook endpoints that can be used to trigger builds when Docker images used by a job have been rebuilt. In CloudBees Docker Hub/Registry Notification Plugin 2.6.2 and earlier, these endpoints can be accessed without authentication. This allows unauthenticated attackers to trigger builds of jobs corresponding to the attacker-specified repository. CloudBees Docker Hub/Registry Notification Plugin 2.6.2.1 requires a token as a part of webhook URLs, which will act as authentication for the webhook endpoint. As a result, all webhook URLs in the plugin will be different after updating the plugin. Administrators can set the Java system property org.jenkinsci.plugins.registry.notification.webhook.JSONWebHook.DONOTREQUIREAPITOKEN to true to disable this fix.

    Recommended action: Upgrade to 2.6.2.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →