# CVE-2023-24434: CSRF vulnerability in Jenkins GitHub Pull Request Builder Plugin

> Attackers can exploit CSRF to connect to malicious URLs using stolen credentials, capturing sensitive data stored in Jenkins.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Jan 2023
- **Updated:** 2 Apr 2025
- **Also known as:** GHSA-m6q8-mwf6-6mmc

## What is CVE-2023-24434?

CVE-2023-24434 is a high-severity vulnerability in Jenkins GitHub Pull Request Builder Plugin, published on 24 Jan 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2023-24434?

2 open source packages ship an affected version, including org.jenkins-ci.plugins:ghprb. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:ghprb` | Maven | All versions to 1.42.2 | None |
| `org.jenkins-ci.plugins:ghprb` | Maven | All versions to 1.42.2 | None |

Products: Jenkins Github Pull Request Builder.

## How do I fix CVE-2023-24434?

No fix has been published for CVE-2023-24434 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-24434 being exploited?

There is no known exploitation of CVE-2023-24434 in the wild and no public exploit code.

## Other vulnerabilities in Jenkins GitHub Pull Request Builder Plugin

- [CVE-2018-1000142](https://insights.sbomify.com/CVE-2018-1000142/): Jenkins GitHub Pull Request Builder Plugin allows attacker with local file system access to obtain GitHub credentials (high 7.8)
- [CVE-2018-1000143](https://insights.sbomify.com/CVE-2018-1000143/): Jenkins GitHub Pull Request Builder Plugin (medium 6.7)
- [CVE-2023-24435](https://insights.sbomify.com/CVE-2023-24435/): Missing permission checks in Jenkins GitHub Pull Request Builder Plugin (medium 6.5)
- [CVE-2018-1000186](https://insights.sbomify.com/CVE-2018-1000186/): Jenkins GitHub Pull Request Builder Plugin credential capture vulnerability (medium 6.5)
- [CVE-2023-24436](https://insights.sbomify.com/CVE-2023-24436/): Jenkins GitHub Pull Request Builder Plugin missing permission check allows enumerating credentials IDs (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-24434 and fix it if it is affected.

What it is: CVE-2023-24434 is a high-severity vulnerability in Jenkins GitHub Pull Request Builder Plugin, published on 24 Jan 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-24434 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:ghprb (Maven): affected all versions up to 1.42.2; no fix listed
- org.jenkins-ci.plugins:ghprb (Maven): affected all versions up to 1.42.2; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-24434/ (Markdown: https://insights.sbomify.com/CVE-2023-24434/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-24434
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-24434
- OSV: https://osv.dev/vulnerability/CVE-2023-24434

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-24434/
Summaries are generated and may contain mistakes; the official description above is the record.