dbcve.org
Gerrit TriggerApplication · Jenkins

CVE-2023-24423

MEDIUM · 6.5 CVSS v3.1 Published 2023-01-26
Fix available
A fix is available. Upgrade to 2.38.1 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 Gerrit Trigger Plugin 2.38.0 and earlier allows attackers to rebuild previous builds triggered by Gerrit.

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 · moderate confidence

Cross-site request forgery (CSRF) vulnerability in Jenkins Gerrit Trigger Plugin versions 2.38.0 and earlier allows unauthenticated attackers to trigger rebuilds of previous builds by tricking authenticated Jenkins users into visiting malicious web pages. The plugin lacks proper CSRF token (crumb) validation on the rebuild endpoint, allowing attackers to forge requests on behalf of authenticated users.

MitigationUpdate Jenkins Gerrit Trigger Plugin to version 2.38.1 or later which includes CSRF protection (crumb) support. Alternatively, ensure Jenkins global security settings require CSRF tokens for API calls.

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
Gerrit TriggerApplication
Affected:< 2.38.1

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 Jenkins Gerrit Trigger plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Gerrit Trigger' in the list of installed plugins
    Affected if The plugin is not found in the installed plugins list, meaning the plugin is not present and this CVE does not apply
  2. Check the installed version of the Gerrit Trigger plugin
    In the installed plugins list, locate the Gerrit Trigger plugin and note the Version column. Compare this version number to the affected range: versions 2.38.0 and earlier (i.e., any version < 2.38.1)
    Affected if The installed version is 2.38.0 or any earlier version number, placing it within the vulnerable range
  3. Confirm the rebuild feature is accessible
    Determine if the Gerrit Trigger rebuild functionality is in use. This can be verified by checking if any jobs are configured with Gerrit Trigger and if users have access to rebuild previous builds via the Gerrit Trigger rebuild button or API endpoint
    Affected if The rebuild endpoint is accessible and usable by authenticated Jenkins users, which is required for the CSRF forged request to be executed
  4. Verify if Jenkins global CSRF protection is enabled
    Navigate to Jenkins > Manage Jenkins > Configure Global Security and locate the 'Crumb Issuer' section under CSRF Protection. Confirm whether CSRF tokens (crumbs) are required for API calls
    Affected if CSRF protection is disabled or set to not require crumbs for API calls, leaving the rebuild endpoint unprotected

A user is affected if the Gerrit Trigger plugin is installed with a version prior to 2.38.1 and the rebuild endpoint is accessible to authenticated users without additional CSRF safeguards.

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 2.38.1 or later
Fixed in 2.38.1
Interim mitigation

Update Jenkins Gerrit Trigger Plugin to version 2.38.1 or later which includes CSRF protection (crumb) support. Alternatively, ensure Jenkins global security settings require CSRF tokens for API calls.

Recommended fix High confidence

Gerrit Trigger Plugin version 2.38.1 or later

  1. Navigate to the Jenkins dashboard
  2. Go to Manage Jenkins > Manage Plugins
  3. Select the 'Installed' tab
  4. Locate the Gerrit Trigger plugin in the list
  5. If the installed version is below 2.38.1, click 'Update' to install the latest version
  6. Restart Jenkins if required to complete the plugin update
  7. Verify the installed version is 2.38.1 or later

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

Fix this in Gerrit Trigger Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-24423 — 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-2023-24423 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