Job GeneratorApplication · Jenkins
CVE-2022-29042
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 Job Generator Plugin 1.22 and earlier does not escape the name and description of Generator Parameter and Generator Choice parameters on Job Generator jobs' Build With Parameters views, 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 Job Generator Plugin versions 1.22 and earlier fails to escape HTML in the name and description fields of Generator Parameter and Generator Choice parameters when rendered on Build With Parameters views. This allows authenticated users with Item/Configure permission to inject malicious scripts that execute in the browsers of other users viewing these pages.
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 GeneratorApplication
<= 1.22CVSS 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 Job Generator Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab, or inspect $JENKINS_HOME/plugins for the job-generator directoryAffected if The plugin is present in the Jenkins environment
-
Determine installed plugin versionIn Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed tab and find Job Generator Plugin version, or read $JENKINS_HOME/plugins/job-generator/META-INF/MANIFEST.MF for the Plugin-Version attributeAffected if Version is 1.22 or earlier (the affected range)
-
Identify jobs using Generator Parameter or Generator ChoiceSearch job config.xml files for <hudson.plugins.jobs.generate.GeneratorParameterDefinition> or <hudson.plugins.jobs.generate.GeneratorChoiceParameterDefinition> elements, or inspect job configuration pages for these parameter typesAffected if Any Jenkins jobs are configured with Generator Parameter or Generator Choice parameters
-
Inspect parameter configuration for HTML contentIn affected jobs, view Configure page and examine the Name and Description fields of Generator Parameter and Generator Choice parameters. Check if fields contain raw HTML tags like <script>, <img src=...>, <a href=...> without encodingAffected if The Name or Description field contains unescaped HTML markup that could execute in a browser
User is affected if Jenkins Job Generator Plugin version 1.22 or earlier is installed AND jobs exist with Generator Parameter or Generator Choice parameters containing raw HTML in their name or description fields.
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 Jenkins Job Generator Plugin to version 1.23 or later which implements proper output encoding for Generator Parameter and Generator Choice field names and descriptions.
Fix this in Job Generator
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-29042 — 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-29042 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