Project InheritanceApplication · Jenkins
CVE-2022-34787
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 Project Inheritance Plugin 21.04.03 and earlier does not escape the reason a build is blocked in tooltips, resulting in a cross-site scripting (XSS) vulnerability exploitable by attackers able to control the reason a queue item is blocked.
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 Project Inheritance Plugin fails to escape the 'blocked build reason' field before rendering it in tooltips, allowing stored XSS. Attackers who can control queue item blocking reasons can inject malicious JavaScript that executes when users view affected tooltips.
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
Project InheritanceApplication
<= 21.04.03CVSS 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.
-
Verify Jenkins Project Inheritance plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or check the plugin directory for the inheritance pluginAffected if The plugin is present in the Jenkins instance
-
Check the installed version of the pluginIn the plugin manager, view the version column for the Project Inheritance plugin, or check the plugin's manifest fileAffected if The version is 21.04.03 or lower
-
Confirm the blocked build reason feature is in useReview Jenkins build queue configurations or job settings that involve blocking builds with custom reasonsAffected if Queue item blocking with custom reasons is configured or was recently used
-
Identify users with permission to set blocking reasonsReview Jenkins authorization matrix or role-based access controls for permissions related to queue item control (such as Overall/Administer or Queue/Configure)Affected if Users beyond administrators can configure queue item blocking reasons
The environment is affected if the Jenkins Project Inheritance plugin version 21.04.03 or lower is installed AND users with access to set queue item blocking reasons exist in the system
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.
dbcve · scopedUpgrade to a patched version of the plugin. As a compensating control, restrict permissions for users who can set queue item blocking reasons until the patch is applied.
Project Inheritance Plugin version 21.04.04 or later
- 1. Log into the Jenkins controller as an administrator with Manage Plugins permission
- 2. Navigate to 'Manage Jenkins' > 'Manage Plugins'
- 3. Go to the 'Installed' tab
- 4. Locate the 'Project Inheritance' plugin in the list
- 5. If the plugin shows version 21.04.03 or earlier, select it and click 'Update'
- 6. After the update completes, restart Jenkins or wait for the plugin to reload
- 7. Verify the plugin is now at version 21.04.04 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Project Inheritance
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-34787 — 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-34787 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