dbcve.org
Github Pull Request BuilderApplication · Jenkins

CVE-2023-24435

MEDIUM · 6.5 CVSS v3.1 Published 2023-01-26
Fix available
A fix is available. Upgrade to after 1.42.2 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 missing permission check in Jenkins GitHub Pull Request Builder Plugin 1.42.2 and earlier allows attackers with Overall/Read permission 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

The Jenkins GitHub Pull Request Builder Plugin versions 1.42.2 and earlier lacks proper permission checks, allowing any user with Overall/Read access to specify arbitrary URLs and credentials IDs to exfiltrate stored Jenkins credentials. This is an authorization bypass where the plugin fails to verify that users have appropriate permissions before allowing credential usage.

MitigationUpgrade the GitHub Pull Request Builder Plugin to version 1.42.3 or later, which includes the missing permission check. If immediate patching is not possible, restrict Overall/Read permission to trusted users only.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 GitHub Pull Request Builder Plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed, or inspect $JENKINS_HOME/plugins/ for github-pull-request-builder.jpi or .hpi
    Affected if Plugin file exists in the plugins directory
  2. Determine installed plugin version
    In Jenkins UI: Manage Jenkins > Manage Plugins > Installed > GitHub Pull Request Builder > Version. Alternatively, unzip the plugin .jpi file and read META-INF/MANIFEST.MF for the Plugin-Version attribute
    Affected if Version listed is 1.42.2 or earlier
  3. Confirm credential configuration
    Navigate to job configuration or global configuration where the plugin stores credentials (often under Build Settings > GitHub Pull Request Builder or Configure System > GitHub > Pull Request Builder). Inspect stored credentials IDs
    Affected if Any credentials IDs are configured for use with the plugin
  4. Audit Overall/Read permission assignments
    Navigate to Manage Jenkins > Manage and Assign Users > Assign Roles, or inspect $JENKINS_HOME/confighudson.security.AuthorizationMatrixProperty if used. Review which users or groups have Overall/Read permission
    Affected if Any user or group with Overall/Read permission is untrusted or outside the security boundary

Environment is affected if GitHub Pull Request Builder Plugin version is 1.42.2 or earlier AND the plugin has configured credentials AND untrusted users possess Overall/Read permission.

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.42.2
Interim mitigation

Upgrade the GitHub Pull Request Builder Plugin to version 1.42.3 or later, which includes the missing permission check. If immediate patching is not possible, restrict Overall/Read permission to trusted users only.

Recommended fix Moderate confidence

GitHub Pull Request Builder version 1.42.3 or later

  1. Navigate to Jenkins dashboard
  2. Go to Manage Jenkins > Manage Plugins
  3. Click on the 'Installed' tab
  4. Locate 'GitHub Pull Request Builder' plugin in the list
  5. If an update is available, select it and click 'Download now and install after restart'
  6. Alternatively, go to the 'Available' tab and search for the plugin to check for newer versions
  7. After upgrading, restart Jenkins to apply the changes
  8. Verify the plugin version is 1.42.3 or later

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

Fix this in Github Pull Request Builder Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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