dbcve.org
Ns Nd Integration Performance PublisherApplication · Jenkins

CVE-2022-45392

MEDIUM · 6.5 CVSS v3.1 Published 2022-11-15
Fix available
A fix is available. Upgrade to 4.8.0.146 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 stores passwords unencrypted in job config.xml files on the Jenkins controller where they can be viewed by attackers with Extended Read permission, or access to the Jenkins controller file system.

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 stores user-provided passwords in plain text within job config.xml files. Attackers with Extended Read permission can view these passwords through the Jenkins UI, or any user with filesystem access to the Jenkins controller can read them directly from the XML configuration files.

MitigationUpgrade to a patched version of the plugin if available. If no patch exists, rotate all passwords that were stored using this plugin and consider removing the plugin until a fix is released. Restrict Extended Read permission to minimize attack surface.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 if the Ns Nd Integration Performance Publisher plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Ns Nd Integration Performance Publisher' or 'NS-ND Integration Performance Publisher', or inspect the plugin directory on the Jenkins controller (typically $JENKINS_HOME/plugins/) for the plugin folder.
    Affected if The plugin is present in the Jenkins installation.
  2. Check the installed version of the plugin
    In the Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed tab and locate the Ns Nd Integration Performance Publisher plugin to view its version number. Alternatively, inspect the plugin's manifest file ( MANIFEST.MF ) within the plugin directory.
    Affected if The installed version is 4.8.0.143 or earlier, or any version below 4.8.0.146.
  3. Identify jobs using the plugin and inspect their config.xml files
    Locate job configuration files in $JENKINS_HOME/jobs/<job-name>/config.xml for each job that uses the Ns Nd Integration Performance Publisher plugin. Open the XML files and search for password-related fields or parameters (look for elements like <password>, <secret>, or credentials configuration).
    Affected if Password or secret values are stored in plain text (unencrypted) within the XML rather than being referenced as credentials IDs or stored in the credentials store.
  4. Verify Extended Read permission is granted to users
    Navigate to Manage Jenkins > Manage Users or check the authorization matrix in Manage Jenkins > Configure Global Security. Review which users or groups have the Extended Read permission enabled.
    Affected if Extended Read permission is granted to any user other than administrators, increasing the risk of unauthorized password exposure through the UI.

A user is affected if the Ns Nd Integration Performance Publisher plugin version is below 4.8.0.146 and the plugin has been used to store passwords in plain text within job configuration files, especially when Extended Read permission is enabled for non-admin 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 4.8.0.146 or later
Fixed in 4.8.0.146
Interim mitigation

Upgrade to a patched version of the plugin if available. If no patch exists, rotate all passwords that were stored using this plugin and consider removing the plugin until a fix is released. Restrict Extended Read permission to minimize attack surface.

Recommended fix High confidence

4.8.0.146 or later

  1. Back up your Jenkins configuration and job configs before making changes
  2. Navigate to Jenkins Manage Plugins > Available tab
  3. Locate 'NS-ND Integration Performance Publisher' in the plugin list
  4. Update the plugin to version 4.8.0.146 or later
  5. Restart Jenkins if required for the plugin update to take effect
  6. Verify the plugin version shows 4.8.0.146 or higher in the Installed tab
  7. If any credentials were stored in job configurations using this plugin, consider rotating those passwords as a precaution

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
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
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,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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