dbcve.org
Matrix ReloadedApplication · Jenkins

CVE-2022-34789

MEDIUM · 6.5 CVSS v3.1 Published 2022-06-30
Fix available
A fix is available. Upgrade to after 1.1.3 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
A cross-site request forgery (CSRF) vulnerability in Jenkins Matrix Reloaded Plugin 1.1.3 and earlier allows attackers to rebuild previous matrix builds.

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 confidence

The Jenkins Matrix Reloaded Plugin versions 1.1.3 and earlier contain a CSRF vulnerability that allows authenticated users to be tricked into unknowingly triggering rebuilds of previous matrix builds. Attackers exploit the lack of anti-CSRF tokens on the rebuild endpoint, leveraging the victim's active session to execute unauthorized build requests.

MitigationUpgrade the Matrix Reloaded Plugin to a version newer than 1.1.3. Additionally, ensure Jenkins global CSRF protection is enabled and review plugin dependencies for similar vulnerabilities.

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
Affected:<= 1.1.3

CVSS 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
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Matrix Reloaded Plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Matrix Reloaded' in the list of installed plugins
    Affected if The plugin appears in the installed plugins list
  2. Check installed plugin version
    In the Installed Plugins tab, locate the Matrix Reloaded plugin and note the Version column displayed
    Affected if The version is 1.1.3 or earlier
  3. Verify rebuild endpoint is accessible
    Attempt to access the rebuild endpoint by navigating to a completed matrix build job and locating any 'Rebuild' or 'Reload' action links, or inspect if the plugin serves HTTP endpoints under /plugin/matrix-reloaded/
    Affected if The rebuild functionality is present and accessible to authenticated users
  4. Confirm active user sessions exist
    Review Jenkins > Manage Jenkins > Users to see authenticated users, or check that Jenkins authentication is enabled and users have active sessions
    Affected if Authenticated users have active sessions that could be exploited via CSRF

If the Matrix Reloaded Plugin version 1.1.3 or earlier is installed with the rebuild feature accessible to authenticated users, the environment is affected by this CSRF vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 1.1.3
Interim mitigation

Upgrade the Matrix Reloaded Plugin to a version newer than 1.1.3. Additionally, ensure Jenkins global CSRF protection is enabled and review plugin dependencies for similar vulnerabilities.

Recommended fix Moderate confidence

Matrix Reloaded plugin version greater than 1.1.3 (check Jenkins Plugin Manager for latest available version)

  1. Navigate to the Jenkins dashboard
  2. Go to Manage Jenkins > Manage Plugins
  3. Select the Installed tab
  4. Locate the Matrix Reloaded plugin in the list
  5. Check if an update is available for the Matrix Reloaded plugin
  6. If an update is available, select the plugin and click 'Download now and install after restart' or 'Update'
  7. Wait for the plugin to update
  8. Restart Jenkins if required

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Matrix Reloaded Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-34789 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-34789 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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