Job And Node OwnershipApplication · Jenkins
CVE-2022-28150
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 · uneditedA cross-site request forgery (CSRF) vulnerability in Jenkins Job and Node ownership Plugin 0.13.0 and earlier allows attackers to change the owners and item-specific permissions of a job.
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 confidenceA cross-site request forgery (CSRF) vulnerability in Jenkins Job and Node ownership Plugin versions 0.13.0 and earlier allows authenticated users to be tricked into unknowingly changing job ownership and item-specific permissions through malicious requests.
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
<= 0.13.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if Job and Node Ownership plugin is installedGo to Manage Jenkins > Manage Plugins > Installed tab, or use the Jenkins CLI: java -jar jenkins-cli.jar list-plugins | grep -i ownershipAffected if Plugin is not installed - not affected. If installed, continue to version check.
-
Verify the installed version of Job and Node Ownership pluginIn Jenkins UI: Manage Jenkins > Manage Plugins > Installed tab > find 'Job and Node Ownership' and note the Version column. Or check the plugin's manifest file (${JENKINS_HOME}/plugins/job-and-node-ownership.jpi or .hpi)Affected if Version is 0.13.0 or earlier - vulnerable to CVE-2022-28150. Version newer than 0.13.0 means not affected by this specific flaw.
-
Confirm the plugin is active/enabledCheck Manage Jenkins > Manage Plugins > Installed tab - the plugin shows as 'Enabled'. Also check ${JENKINS_HOME}/plugins/job-and-node-ownership.jpi.disabled does not exist (or check via Jenkins CLI)Affected if Plugin is installed with version <= 0.13.0 AND enabled - fully affected by the CSRF vulnerability. If disabled, the attack surface is reduced but the vulnerable code may still exist.
A user is affected if the Jenkins Job and Node Ownership plugin is installed, enabled, and running version 0.13.0 or earlier, allowing CSRF attacks to modify job ownership without the user's knowledge.
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 dataUpdate Jenkins Job and Node ownership Plugin to a version newer than 0.13.0, and ensure Jenkins is configured to enforce CSRF protection (which is the default in modern Jenkins versions).
Fix this in Job And Node Ownership
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28150 — 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-28150 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