dbcve.org
Job And Node OwnershipApplication · Jenkins

CVE-2022-28149

MEDIUM · 5.4 CVSS v3.1 Published 2022-03-29
Fix available
A fix is available. Upgrade to after 0.13.0 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 Job and Node ownership Plugin 0.13.0 and earlier does not escape the names of the secondary owners, 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 confidence

The Jenkins Job and Node Ownership Plugin versions 0.13.0 and earlier fails to properly sanitize secondary owner names before displaying them in the web UI, leading to a stored cross-site scripting (XSS) vulnerability. Attackers with Item/Configure permission can inject malicious JavaScript into owner name fields that will execute when other users view the ownership configuration.

MitigationUpgrade the Jenkins Job and Node Ownership Plugin to version 0.14.0 or later which includes proper output encoding. As an interim control, restrict Item/Configure permission 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
Job And Node OwnershipApplication
Affected:<= 0.13.0

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Check plugin version
    In Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab. Find 'Job and Node Ownership' plugin and note the version number listed.
    Affected if The version listed is 0.13.0 or earlier.
  2. Verify secondary ownership feature is in use
    Navigate to a Jenkins job configuration page. Look for the 'Ownership' section and check if the 'Secondary Owners' field contains any entries.
    Affected if Secondary owners are configured and the plugin version is 0.13.0 or earlier.
  3. Inspect page source for unsanitized output
    View the job configuration page (or ownership configuration) in a browser. Right-click and view page source. Search for the secondary owner name strings and examine if they appear as raw text or are properly encoded (e.g., look for &lt;script&gt; tags or unescaped special characters).
    Affected if Owner names appear in the HTML without encoding (visible <, >, or & characters when they should be encoded).
  4. Audit Item/Configure permissions
    Go to Manage Jenkins > Manage and Assign Roles > Manage Roles. Review which users or groups have Item/Configure permission on the relevant projects or globally.
    Affected if Untrusted users or groups have Item/Configure permission and the plugin version is 0.13.0 or earlier.

The environment is affected if the Job and Node Ownership Plugin version is 0.13.0 or earlier AND secondary owners are configured AND untrusted users have Item/Configure permission.

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 a release after 0.13.0
Interim mitigation

Upgrade the Jenkins Job and Node Ownership Plugin to version 0.14.0 or later which includes proper output encoding. As an interim control, restrict Item/Configure permission to trusted users only.

Recommended fix Moderate confidence

Upgrade to Job and Node Ownership plugin version 0.13.1 or later

  1. Navigate to Manage Jenkins > Manage Plugins > Installed
  2. Locate the 'Job and Node Ownership' plugin in the 'Installed' tab
  3. Check the current version - if it is 0.13.0 or earlier, an update is required
  4. Select the plugin and click 'Update' to install the latest version
  5. After updating, verify the new version is 0.13.1 or higher in the Installed plugins list
  6. Restart Jenkins if prompted or restart the Jenkins service to ensure the update takes effect

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Job And Node Ownership Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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