dbcve.org
Github Pull Request BuilderApplication · Jenkins

CVE-2023-24434

HIGH · 8.8 CVSS v3.1 Published 2023-01-26
Fix available
A fix is available. Upgrade to after 1.42.2 or later.
See remediation →
95/100
Remediation priority · Urgent
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 GitHub Pull Request Builder Plugin 1.42.2 and earlier allows attackers to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.

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

This is a CSRF vulnerability in the Jenkins GitHub Pull Request Builder Plugin (version 1.42.2 and earlier). The flaw allows attackers to trigger Jenkins to make outbound connections to attacker-controlled URLs using credentials IDs that they specify, potentially exfiltrating stored Jenkins credentials that match those IDs.

MitigationUpdate the Jenkins GitHub Pull Request Builder Plugin to a version newer than 1.42.2, or disable the plugin if not in use.

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
Github Pull Request BuilderApplication
Affected:<= 1.42.2

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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 GitHub Pull Request Builder plugin is installed
    Log into Jenkins as an administrator, navigate to Manage Jenkins > Manage Plugins > Installed tab, and search for 'GitHub Pull Request Builder' or 'ghprb' in the list of installed plugins. Alternatively, check the plugin manifest file at $JENKINS_HOME/plugins/ghprb/META-INF/MANIFEST.MF
    Affected if The plugin appears in the list of installed plugins
  2. Check the installed plugin version
    In the Installed Plugins list, locate the GitHub Pull Request Builder plugin and note the Version column. If using CLI, run: jenkins-plugin-cli --list --filter ghprb or inspect the MANIFEST.MF file for the Plugin-Version attribute
    Affected if The version listed is 1.42.2 or earlier, or if the version cannot be determined (older plugin without version metadata)
  3. Confirm plugin is enabled and loaded
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and verify the GitHub Pull Request Builder plugin shows as 'Enabled'. Check the Jenkins logs at $JENKINS_HOME/logs for entries containing 'ghprb' or 'GitHub Pull Request Builder' during startup to confirm the plugin loaded successfully
    Affected if The plugin is enabled and was loaded by Jenkins at startup
  4. Identify if the plugin API is accessible
    Check if the Jenkins web UI responds to /ghprb/ endpoints or review Jenkins security configuration under Manage Jenkins > Global Security to see if the plugin exposes any unauthenticated or CSRF-vulnerable endpoints. Use a tool like curl to probe: curl -s -o /dev/null -w '%{http_code}' http://YOUR_JENKINS/ghprb/api/json
    Affected if The plugin API endpoints are accessible without proper CSRF protection (the vulnerable condition)
  5. Review credential usage in plugin configuration
    Navigate to the plugin configuration page (typically under Manage Jenkins > Configure System > GitHub Pull Request Builder or job-specific configuration) and identify any configured credentials. Note the credential IDs configured, as these are the IDs an attacker could target in an exploit
    Affected if Credentials are configured and assigned to the plugin (exposing them to potential exfiltration via the CSRF flaw)

You are affected if the GitHub Pull Request Builder plugin is installed, enabled, running version 1.42.2 or earlier, and has credentials configured for its use.

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.

From vendor data
Upgrade available Upgrade to a release after 1.42.2
Interim mitigation

Update the Jenkins GitHub Pull Request Builder Plugin to a version newer than 1.42.2, or disable the plugin if not in use.

Fix this in Github Pull Request Builder Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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