Promoted BuildsApplication · Jenkins
CVE-2022-30965
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 Promoted Builds (Simple) Plugin 1.9 and earlier does not escape the name and description of Promotion Level parameters on views displaying parameters, 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 confidenceThe Jenkins Promoted Builds (Simple) Plugin versions 1.9 and earlier fails to properly escape the name and description fields of Promotion Level parameters when rendering them on parameter display views. This allows an attacker with Item/Configure permission to inject malicious JavaScript code into these fields, which is then stored and executed in the browsers of other users who view the affected parameter displays.
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
Promoted BuildsApplication
<= 1.9CVSS 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.
-
Check Promoted Builds plugin versionNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Promoted Builds (Simple)' or 'promoted-builds-simple' plugin. Note the version displayed.Affected if Plugin version is 1.9 or earlier
-
Verify Promotion Processes existGo to a Jenkins job that uses Promoted Builds. Click on 'Promotions' in the job's sidebar. Check if any promotion processes are configured.Affected if At least one Promotion Process is configured for any job
-
Examine Promotion Level parameter namesIn the promotion process configuration, look for the 'Promotion Level' section under 'Actions'. Click on the parameter name field and inspect if it contains HTML or script tags (such as <script>, <img onerror=>, javascript:, etc.).Affected if The parameter name field contains unescaped HTML or JavaScript content
-
Examine Promotion Level parameter descriptionsIn the same Promotion Level configuration, check the 'Description' field for the parameter. Inspect whether it contains HTML tags, script elements, or event handlers.Affected if The description field contains unescaped HTML or JavaScript content
-
Check rendered parameter displayView the job or promotion status page in a browser. Right-click and 'View Page Source' or inspect the Promotion Level parameter section to see if the name/description is rendered with proper HTML escaping (e.g., < instead of <).Affected if The rendered HTML shows raw unescaped characters like <script> rather than <script>
If the Promoted Builds (Simple) Plugin version 1.9 or earlier is installed AND Promotion Level parameters contain unescaped HTML/script content in their name or description fields that renders as raw HTML, the environment is affected by this stored XSS vulnerability.
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 Promoted Builds (Simple) Plugin to version 1.10 or later, which implements proper HTML escaping for Promotion Level parameter names and descriptions.
Fix this in Promoted Builds
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30965 — 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-30965 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