Matrix ReloadedApplication · Jenkins
CVE-2022-34788
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 Matrix Reloaded Plugin 1.1.3 and earlier does not escape the agent name in tooltips, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Agent/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 Matrix Reloaded Plugin versions 1.1.3 and earlier fail to properly escape agent names before rendering them in tooltips. An attacker with Agent/Configure permission can inject malicious JavaScript code into an agent's name, which gets stored and executed in the browsers of other users viewing the agent configuration page.
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
Matrix ReloadedApplication
<= 1.1.3CVSS 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 Matrix Reloaded plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab, or check the file $JENKINS_HOME/plugins/matrix-reloaded/META-INF/MANIFEST.MF for the plugin versionAffected if The plugin is present in the Jenkins instance
-
Determine the installed version of Matrix ReloadedIn the plugin manager UI, locate Matrix Reloaded in the Installed tab and note the Version column; alternatively, read the Version header from the MANIFEST.MF fileAffected if The reported version is 1.1.3 or earlier
-
Confirm no fix version is appliedCheck if the plugin has received updates since version 1.1.3 by viewing the plugin details page or checking for a more recent version in the Updates tabAffected if The plugin remains at version 1.1.3 or earlier with no subsequent update installed
-
Identify if agents exist with user-configurable namesNavigate to Manage Jenkins > Manage Nodes and Agents, then review the list of configured agents and their display namesAffected if Any agents are configured in Jenkins, as the XSS payload would be stored in agent names
-
Check for presence of malicious script in agent namesInspect each agent's name field in the agent configuration (click the agent name) and view the page source or use the Jenkins API (GET /computer/{agent}/api/json) to review the displayName valueAffected if Agent names contain unsanitized HTML or JavaScript characters like <script>, onerror=, or javascript: alerts
You are affected if the Matrix Reloaded plugin version is 1.1.3 or earlier and any agents are configured in Jenkins, as the stored XSS in agent name tooltips can be triggered when other users view the agent configuration.
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 Matrix Reloaded Plugin to version 1.1.4 or later, which includes proper output encoding for agent names in tooltips.
Fix this in Matrix Reloaded
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-34788 — 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-34788 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