Ns Nd Integration Performance PublisherApplication · Jenkins
CVE-2022-41229
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 · uneditedJenkins NS-ND Integration Performance Publisher Plugin 4.8.0.134 and earlier does not escape configuration options of the Execute NetStorm/NetCloud Test build step, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Item/Configure permission.
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 confidenceThe Jenkins NS-ND Integration Performance Publisher Plugin versions 4.8.0.134 and earlier fail to properly escape/sanitize configuration options for the 'Execute NetStorm/NetCloud Test' build step. This allows a stored XSS payload to be injected via these configuration fields. When other users view the job configuration, the malicious JavaScript executes within their session.
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
<= 4.8.0.134CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check if NS-ND Integration Performance Publisher plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'NS-ND Integration Performance Publisher' or use the Jenkins script console: Jenkins.instance.pluginManager.plugins.find{it.shortName=='ns-nd-integration-performance-publisher'}?.versionAffected if Plugin is installed and version is 4.8.0.134 or earlier
-
Identify jobs using the Execute NetStorm/NetCloud Test build stepUse Jenkins script console to search: Jenkins.instance.allItems.findAll{job -> job.allActions.any{action -> action.class.name.contains('NetStormNetCloudTest')}} or manually review job configurations for this build step typeAffected if Any job in the instance uses the Execute NetStorm/NetCloud Test build step
-
Inspect job configuration XML for injected scriptsNavigate to a job using the build step, go to Configure, view the source XML (or use /job/[name]/config.xml API), and examine fields in the netStormNetCloudTest section for script tags, event handlers, or suspicious encoded contentAffected if Configuration contains JavaScript in any field (src, arguments, or other parameters) that could execute when the page loads
You are affected if the NS-ND Integration Performance Publisher plugin version is 4.8.0.134 or earlier AND any job in your instance uses the Execute NetStorm/NetCloud Test build step with potentially malicious configuration values.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade the NS-ND Integration Performance Publisher Plugin to a version newer than 4.8.0.134. Until then, restrict Item/Configure permission to trusted users only and audit existing job configurations for suspicious payloads.
Fix this in Ns Nd Integration Performance Publisher
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41229 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-41229 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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