OntrackApplication · Jenkins
CVE-2022-34192
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 ontrack Jenkins Plugin 4.0.0 and earlier does not escape the name of Ontrack: Multi Parameter choice, Ontrack: Parameter choice, and Ontrack: SingleParameter 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 ontrack plugin versions 4.0.0 and earlier fail to escape parameter names (Ontrack: Multi Parameter choice, Ontrack: Parameter choice, and Ontrack: SingleParameter) before rendering them in the UI, allowing stored XSS via malicious parameter names. Attackers with Item/Configure permission can inject JavaScript that executes when other users view the parameter display.
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
OntrackApplication
<= 4.0.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
- 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.
-
Identify ontrack plugin versionIn Jenkins, go to Manage Jenkins > Manage Plugins > Installed and locate the ontrack plugin to confirm its version numberAffected if The installed version is 4.0.0 or earlier
-
Check for affected parameter types in useReview Jenkins jobs that utilize the Ontrack: Multi Parameter choice, Ontrack: Parameter choice, or Ontrack: SingleParameter parameter typesAffected if Any job is using one of the three affected parameter types (Ontrack: Multi Parameter choice, Ontrack: Parameter choice, or Ontrack: SingleParameter)
-
Inspect parameter names for XSS patternsExamine the configured parameter names in jobs using the affected parameter types, looking for unusual characters, script tags, or HTML markup that may indicate injected payloadsAffected if Any parameter name contains script tags, event handlers, or other XSS payloads
-
Review Item/Configure permission assignmentsCheck which users or groups have Item/Configure permission, particularly on jobs using the affected parameter typesAffected if Users with Item/Configure permission on jobs with affected parameters are untrusted or include external users
You are affected if the ontrack plugin version is 4.0.0 or earlier AND any jobs use the Ontrack parameter types with untrusted users having Item/Configure permission.
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 ontrack plugin to a version after 4.0.0 that properly escapes parameter names. As a compensating control, restrict Item/Configure permission to trusted users only.
Fix this in Ontrack
Scoped from the published advisory
- Consultation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-34192 — 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-34192 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