dbcve.org
Ns Nd Integration Performance PublisherApplication · Jenkins

CVE-2022-41228

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 →
94/100
Remediation priority · Urgent
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
A missing permission check in Jenkins NS-ND Integration Performance Publisher Plugin 4.8.0.129 and earlier allows attackers with Overall/Read permissions 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

The Jenkins NS-ND Integration Performance Publisher Plugin versions 4.8.0.129 and earlier lacks a permission check in functionality that allows connections to attacker-specified webservers using attacker-specified credentials. Any user with Overall/Read permission can trigger this network connection to an attacker-controlled server, enabling potential data exfiltration or SSRF-style attacks.

MitigationUpgrade the NS-ND Integration Performance Publisher Plugin to version 4.8.0.130 or later, which includes the missing permission check. If immediate upgrade is not possible, restrict Overall/Read permissions to trusted users only.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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. Verify if 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' to confirm the plugin is present in the environment.
    Affected if The plugin is listed as installed in the Jenkins plugin manager.
  2. Check the installed plugin version
    In the Installed plugins tab, locate the NS-ND Integration Performance Publisher Plugin and note the version number displayed. Compare this version against the affected range: versions 4.8.0.129 and earlier.
    Affected if The installed version is 4.8.0.129 or earlier, or if the version cannot be determined and the plugin is present.
  3. Confirm Overall/Read permission is enabled for users
    Navigate to Jenkins > Manage Jenkins > Manage Users and verify that the Overall/Read permission is available to users beyond administrators. This permission is enabled by default in Jenkins.
    Affected if Overall/Read permission is granted to non-admin users, allowing any authenticated user to access the vulnerable functionality.
  4. Identify if the vulnerable connection feature is accessible
    Check if the plugin's functionality that allows configuring connections to external webservers is reachable. This typically involves accessing the plugin's configuration area in job settings or global configuration.
    Affected if The plugin configuration interface is accessible to users with Overall/Read permission, allowing them to specify attacker-controlled server URLs and credentials.

A user is affected if the NS-ND Integration Performance Publisher Plugin is installed at version 4.8.0.129 or earlier AND users with Overall/Read permission can access the plugin's connection configuration features.

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 the NS-ND Integration Performance Publisher Plugin to version 4.8.0.130 or later, which includes the missing permission check. If immediate upgrade is not possible, restrict Overall/Read permissions to trusted users only.

Recommended fix High confidence

4.8.0.130

  1. Log in to Jenkins with administrator credentials
  2. Navigate to 'Manage Jenkins'
  3. Click on 'Manage Plugins'
  4. Go to the 'Updates' tab
  5. Locate 'NS-ND Integration Performance Publisher' in the list
  6. Select the plugin and click 'Download now and install after restart'
  7. Wait for the plugin to download
  8. Restart Jenkins to complete the installation

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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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