Job And Node OwnershipApplication · Jenkins
CVE-2018-1000107
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 · uneditedAn improper authorization vulnerability exists in Jenkins Job and Node Ownership Plugin 0.11.0 and earlier in OwnershipDescription.java, JobOwnerJobProperty.java, and OwnerNodeProperty.java that allow an attacker with Job/Configure or Computer/Configure permission and without Ownership related permissions to override ownership metadata.
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 Job and Node Ownership Plugin 0.11.0 and earlier contains an improper authorization vulnerability where users with Job/Configure or Computer/Configure permissions can bypass ownership permission checks and override ownership metadata. The affected files (OwnershipDescription.java, JobOwnerJobProperty.java, OwnerNodeProperty.java) fail to verify that users possess the required Ownership permissions before allowing configuration changes.
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.11.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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.
-
Verify the plugin is installedGo to Manage Jenkins > Manage Plugins > Installed and search for 'Job and Node Ownership' or check the plugin directory $JENKINS_HOME/plugins for ownership* plugin filesAffected if The plugin is not installed then this CVE does not apply
-
Check the installed plugin versionIn Manage Jenkins > Manage Plugins > Installed, find the Job and Node Ownership plugin and note the version number. Alternatively, inspect the plugin's manifest file (META-INF/MANIFEST.MF) inside the plugin archiveAffected if Version is 0.11.0 or earlier, indicating the vulnerable version is in use
-
Identify users with Job/Configure permissionNavigate to Manage Jenkins > Manage and Assign Roles > Manage Roles. Review the 'Job' permissions assigned to each role, specifically the 'Configure' permission. Or check individual user permissions under People if matrix-based security is usedAffected if Non-admin or untrusted users have Job/Configure permission, which combined with the vulnerable plugin allows them to bypass ownership checks
-
Identify users with Computer/Configure permissionNavigate to Manage Jenkins > Manage and Assign Roles > Manage Roles. Review the 'Computer' (Node) permissions assigned to each role, specifically the 'Configure' permission. Check node configuration access for roles with Computer/ConfigureAffected if Non-admin or untrusted users have Computer/Configure permission, which combined with the vulnerable plugin allows them to bypass node ownership checks
You are affected if the Job and Node Ownership plugin version is 0.11.0 or earlier AND any user with Job/Configure or Computer/Configure permission is not also granted full Ownership permissions, allowing them to bypass ownership authorization controls.
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 Jenkins Job and Node Ownership Plugin to a version after 0.11.0 that includes proper authorization checks. Until then, restrict Job/Configure and Computer/Configure permissions to only trusted users who should also have ownership configuration rights.
Fix this in Job And Node Ownership
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1000107 — 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-2018-1000107 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