dbcve.org
Ns Nd Integration Performance PublisherApplication · Jenkins

CVE-2022-45391

HIGH · 7.5 CVSS v3.1 Published 2022-11-15
Fix available
A fix is available. Upgrade to 4.8.0.146 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
Jenkins NS-ND Integration Performance Publisher Plugin 4.8.0.143 and earlier globally and unconditionally disables SSL/TLS certificate and hostname validation for the entire Jenkins controller JVM.

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 Jenkins NS-ND Integration Performance Publisher Plugin versions 4.8.0.143 and earlier globally disable SSL/TLS certificate and hostname validation across the entire Jenkins controller JVM. This means all outbound HTTPS connections from Jenkins lose their security guarantees, enabling potential man-in-the-middle attacks against any network communication from the controller.

MitigationUpgrade the plugin to a version that does not disable SSL/TLS validation globally, or remove the plugin if no fixed version is available. After remediation, verify that all Jenkins network communications properly validate certificates.

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
Ns Nd Integration Performance PublisherApplication
Affected:< 4.8.0.146

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. Identify if the NS-ND Integration Performance Publisher plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab, or list plugins via Jenkins CLI: java -jar jenkins-cli.jar -s http://localhost:8080 list-plugins
    Affected if The plugin appears in the list of installed plugins
  2. Check the installed version of the NS-ND Integration Performance Publisher plugin
    Locate the plugin file in $JENKINS_HOME/plugins/ (typically named ns-nd-integration-performance-publisher.jpi or as a directory), then inspect the MANIFEST.MF file inside for the Implementation-Version attribute, or view the version directly in the Jenkins UI plugin details
    Affected if The reported version is 4.8.0.143 or earlier, or any version below 4.8.0.146
  3. Verify whether SSL/TLS validation is being disabled globally
    Search the plugin JAR file or extracted plugin directory for code that sets trust manager or hostname verifier to accept all, such as references to TrustManager, AcceptAllTrustManager, or hostnameVerifier configuration; also check Jenkins script console for any global SSL-disabling code: Manage Jenkins > Script Console and search for TrustManager or hostnameVerifier settings
    Affected if Code or configuration is found that disables SSL certificate or hostname validation across the JVM

If the NS-ND Integration Performance Publisher plugin is installed at version 4.8.0.143 or earlier, or if SSL/TLS validation is found to be globally disabled in the Jenkins environment, the system is affected by this CVE.

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 4.8.0.146 or later
Fixed in 4.8.0.146
Interim mitigation

Upgrade the plugin to a version that does not disable SSL/TLS validation globally, or remove the plugin if no fixed version is available. After remediation, verify that all Jenkins network communications properly validate certificates.

Recommended fix High confidence

4.8.0.146 or later

  1. Log in to Jenkins as an administrator
  2. Navigate to 'Manage Jenkins' > 'Manage Plugins'
  3. Go to the 'Updates' tab
  4. Locate 'NS-ND Integration Performance Publisher' in the list
  5. Select the plugin and click 'Download now and install after restart'
  6. After the download completes, restart Jenkins to apply the update
  7. Alternatively, navigate to 'Manage Plugins' > 'Available' tab and search for the latest version of the plugin
  8. Verify the installed version is 4.8.0.146 or later under 'Manage Plugins' > 'Installed' tab

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

Fix this in Ns Nd Integration Performance Publisher Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-45391 — 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-45391 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