Skip to main content
VulnerabilityPublished Updated

CVE-2022-41228: Jenkins NS-ND Integration Performance Publisher Plugin · Missing Authorization

Affects Jenkins NS-ND Integration Performance Publisher PluginSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.9% chance of exploitation in 30 days – higher than 61% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Sep 2022

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Jenkins project Jenkins NS-ND Integration Performance Publisher PluginAffected
  • <=4.8.0.129
Fixed in–

AI-suggested

  1. Immediate verification of the Jenkins NS-ND Integration Performance Publisher Plugin version in use and upgrade to the latest version once a patch is released by the Jenkins project.
  2. Until a patch is available, restrict Overall/Read permissions strictly to trusted users only, minimizing the attack surface.
  3. Implement network-level controls to monitor and restrict outbound connections from Jenkins servers, preventing unauthorized connections to external attacker-controlled servers.
  4. Employ application-layer firewalls or proxy solutions that can detect and block suspicious traffic originating from Jenkins instances.
  5. Conduct regular audits of Jenkins user permissions and plugin usage to ensure adherence to the principle of least privilege.
  6. Monitor Jenkins logs for unusual connection attempts or authentication activities that could indicate exploitation attempts.
  7. Consider isolating Jenkins servers within segmented network zones with limited external connectivity to reduce exposure.
  8. Stay informed through Jenkins security advisories and subscribe to vulnerability notification services to respond promptly to updates.

Description

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.

References

Community reviews

Loading reviews…