dbcve.org
Ns Nd Integration Performance PublisherApplication · Jenkins

CVE-2022-41227

HIGH · 8.8 CVSS v3.1 Published 2022-09-21
Fix available
A fix is available. Upgrade to 4.8.0.130 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 cross-site request forgery (CSRF) vulnerability in Jenkins NS-ND Integration Performance Publisher Plugin 4.8.0.129 and earlier allows attackers to connect to an attacker-specified webserver using attacker-specified credentials.

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

This is a CSRF vulnerability in the Jenkins NS-ND Integration Performance Publisher Plugin that allows authenticated administrators to be tricked into making unintended requests. Attackers can force the plugin to connect to attacker-controlled webservers using attacker-supplied credentials, potentially enabling data exfiltration or further attacks.

MitigationUpgrade to a patched version of the plugin once available, or implement proper CSRF token validation (e.g., Jenkins crumb) on all forms and API endpoints within the plugin.

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.130

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Confirm plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab, or run: java -jar jenkins-cli.jar -s http://localhost:8080 list-plugins (if CLI is available), or inspect the $JENKINS_HOME/plugins/ directory for a folder starting with 'ns-nd' or 'ns_nd'
    Affected if The NS-ND Integration Performance Publisher plugin appears in the installed plugins list
  2. Identify the installed plugin version
    In the Jenkins UI under Manage Jenkins > Manage Plugins > Installed, find the NS-ND Integration Performance Publisher plugin and note the version number shown in the plugin table
    Affected if The version number displayed is lower than 4.8.0.130
  3. Verify plugin is active and loaded
    Check the Jenkins logs or confirm the plugin status shows 'Enabled' in the plugin management UI; confirm the plugin contributes build steps or publishers to job configurations
    Affected if The plugin is installed, enabled, and actively contributes functionality to Jenkins jobs

A user is affected if the NS-ND Integration Performance Publisher plugin is installed with a version below 4.8.0.130 and the plugin is enabled in their Jenkins instance.

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.130 or later
Fixed in 4.8.0.130
Interim mitigation

Upgrade to a patched version of the plugin once available, or implement proper CSRF token validation (e.g., Jenkins crumb) on all forms and API endpoints within the plugin.

Recommended fix High confidence

Upgrade to NS-ND Integration Performance Publisher version 4.8.0.130 or later

  1. 1. Backup your Jenkins configuration and plugin directory as a precaution
  2. 2. Navigate to Jenkins dashboard > Manage Jenkins > Manage Plugins
  3. 3. Go to the 'Updates' tab or 'Available' tab
  4. 4. Locate the 'NS-ND Integration Performance Publisher' plugin in the plugin list
  5. 5. If an update is available, select the plugin and click 'Download now and install after restart' or 'Install'
  6. 6. Wait for the plugin to download and install
  7. 7. Restart Jenkins (or wait for pending restarts if using the 'Download now and install after restart' option)
  8. 8. Verify the plugin has been updated to version 4.8.0.130 or later by going to Manage Jenkins > 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
  • Consultation1.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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