dbcve.org
Cloudbees Docker Hub\/registry NotificationApplication · Jenkins

CVE-2022-45385

HIGH · 7.5 CVSS v3.1 Published 2022-11-15
Fix available
A fix is available. Upgrade to 2.6.2.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A missing permission check in Jenkins CloudBees Docker Hub/Registry Notification Plugin 2.6.2 and earlier allows unauthenticated attackers to trigger builds of jobs corresponding to the attacker-specified repository.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The CloudBees Docker Hub/Registry Notification Plugin for Jenkins versions 2.6.2 and earlier lacks proper permission validation in its build trigger endpoint. This allows any unauthenticated attacker to cause Jenkins to initiate builds for arbitrary repository names by sending crafted requests, leading to unauthorized build execution and potential resource consumption or pipeline manipulation.

MitigationUpdate the CloudBees Docker Hub/Registry Notification Plugin to the latest version to include the missing permission check. If an update is unavailable, disable the plugin or restrict access at the Jenkins proxy/firewall level until a patch is released.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Cloudbees Docker Hub\/registry NotificationApplication
Affected:< 2.6.2.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify the CloudBees Docker Hub/Registry Notification Plugin is installed
    Log in to Jenkins as an administrator, go to Manage Jenkins > Manage Plugins > Installed tab, and search for 'CloudBees Docker Hub' or 'Docker Hub Notification' in the list of installed plugins.
    Affected if The plugin appears in the installed plugins list.
  2. Check the installed plugin version
    In the same Manage Plugins > Installed tab, locate the CloudBees Docker Hub/Registry Notification plugin and note the version number displayed in the Version column.
    Affected if The version number is 2.6.2 or earlier, or the version shows as 2.6.2.1 but you are uncertain whether it was applied before the fix.
  3. Confirm if any jobs use the Docker Hub build trigger
    Go to Jenkins > Manage Jenkins > Script Console and run: Jenkins.instance.allItems.each { job -> job.triggers.each { name, trigger -> if (trigger.class.name.contains('DockerHubTrigger')) { println job.fullName } } }
    Affected if Any jobs are returned by this script, meaning the build trigger is configured and active.
  4. Check if Jenkins is accessible to unauthenticated users
    Attempt to access the Jenkins base URL from an incognito/private browser window without logging in, or review your firewall/networkACL rules allowing external access to the Jenkins HTTP port.
    Affected if The Jenkins UI or build trigger endpoint is reachable without authentication from an untrusted network.

You are affected if the CloudBees Docker Hub/Registry Notification Plugin is installed with version 2.6.2 or earlier, the Docker Hub build trigger is configured on any job, and your Jenkins instance or this specific endpoint is accessible to unauthenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.6.2.1 or later
Fixed in 2.6.2.1
Interim mitigation

Update the CloudBees Docker Hub/Registry Notification Plugin to the latest version to include the missing permission check. If an update is unavailable, disable the plugin or restrict access at the Jenkins proxy/firewall level until a patch is released.

Recommended fix High confidence

2.6.2.1 or later

  1. 1. Navigate to Jenkins dashboard
  2. 2. Go to 'Manage Jenkins' → 'Manage Plugins'
  3. 3. Click on the 'Installed' tab
  4. 4. Search for 'CloudBees Docker Hub/Registry Notification' plugin
  5. 5. If an update is available, click 'Update now' or download version 2.6.2.1 from the Jenkins plugin repository
  6. 6. Restart Jenkins to complete the plugin update
  7. 7. Verify the plugin shows version 2.6.2.1 or later under 'Manage Plugins' → 'Installed'

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cloudbees Docker Hub\/registry Notification Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-45385 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-45385 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data