What is CVE-2022-45385?

CVE-2022-45385 is a medium-severity missing authorization vulnerability in org.jenkins-ci.plugins:dockerhub-notification (maven), affecting versions <= 2.6.2. It is fixed in 2.6.2.1. The application does not perform an authorization check before performing a sensitive operation.

How severe is CVE-2022-45385?

CVE-2022-45385 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of org.jenkins-ci.plugins:dockerhub-notification are affected by CVE-2022-45385?

org.jenkins-ci.plugins:dockerhub-notification (maven) versions <= 2.6.2 is affected.

Is there a fix for CVE-2022-45385?

Yes. CVE-2022-45385 is fixed in 2.6.2.1. Upgrade to this version or later.

Is CVE-2022-45385 exploitable, and should I be worried?

Whether CVE-2022-45385 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2022-45385 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2022-45385

Q: How severe is CVE-2022-45385?

CVE-2022-45385 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of org.jenkins-ci.plugins:dockerhub-notification are affected by CVE-2022-45385?

org.jenkins-ci.plugins:dockerhub-notification (maven) versions <= 2.6.2 is affected.

Q: Is there a fix for CVE-2022-45385?

Yes. CVE-2022-45385 is fixed in 2.6.2.1. Upgrade to this version or later.

Q: Is CVE-2022-45385 exploitable, and should I be worried?

Whether CVE-2022-45385 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2022-45385 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2022-45385?

Upgrade org.jenkins-ci.plugins:dockerhub-notification to 2.6.2.1 or later.

Summary

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

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.DO_NOT_REQUIRE_API_TOKEN to true to disable this fix.

Impact

The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.

CVE-2022-45385 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.6.2.1); upgrading removes the vulnerable code path.

Affected versions

org.jenkins-ci.plugins:dockerhub-notification (<= 2.6.2)

Security releases

org.jenkins-ci.plugins:dockerhub-notification → 2.6.2.1 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade org.jenkins-ci.plugins:dockerhub-notification to 2.6.2.1 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2022-45385? CVE-2022-45385 is a medium-severity missing authorization vulnerability in org.jenkins-ci.plugins:dockerhub-notification (maven), affecting versions <= 2.6.2. It is fixed in 2.6.2.1. The application does not perform an authorization check before performing a sensitive operation.
How severe is CVE-2022-45385? CVE-2022-45385 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of org.jenkins-ci.plugins:dockerhub-notification are affected by CVE-2022-45385? org.jenkins-ci.plugins:dockerhub-notification (maven) versions <= 2.6.2 is affected.
Is there a fix for CVE-2022-45385? Yes. CVE-2022-45385 is fixed in 2.6.2.1. Upgrade to this version or later.
Is CVE-2022-45385 exploitable, and should I be worried? Whether CVE-2022-45385 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2022-45385 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2022-45385? Upgrade org.jenkins-ci.plugins:dockerhub-notification to 2.6.2.1 or later.