# CVE-2022-43421: Jenkins Tuleap Git Branch Source Plugin allows unauthenticated attackers to trigger Tuleap projects whose configured repo matches attacker-specified value

> Unauthenticated attackers can trigger Tuleap projects with matching repositories due to missing permission checks in the Jenkins plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Oct 2022
- **Updated:** 8 May 2025
- **Also known as:** GHSA-73v5-w6fg-2m44

## What is CVE-2022-43421?

CVE-2022-43421 is a medium-severity missing authorization vulnerability in Jenkins Tuleap Git Branch Source Plugin, published on 19 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A missing permission check in Jenkins Tuleap Git Branch Source Plugin 3.2.4 and earlier allows unauthenticated attackers to trigger Tuleap projects whose configured repository matches the attacker-specified value.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2022-43421?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:tuleap-git-branch-source` | Maven | All versions | 3.2.5 |
| `org.jenkins-ci.plugins:tuleap-git-branch-source` | Maven | All versions | 3.2.5 |

Products: Jenkins Tuleap Git Branch Source.

## How do I fix CVE-2022-43421?

Upgrade org.jenkins-ci.plugins:tuleap-git-branch-source to 3.2.5 or later.

## Is CVE-2022-43421 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-43421 and fix it if it is affected.

What it is: CVE-2022-43421 is a medium-severity missing authorization vulnerability in Jenkins Tuleap Git Branch Source Plugin, published on 19 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-43421 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:tuleap-git-branch-source (Maven): affected all versions; fixed in 3.2.5
- org.jenkins-ci.plugins:tuleap-git-branch-source (Maven): affected all versions; fixed in 3.2.5

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-2022-43421/ (Markdown: https://insights.sbomify.com/CVE-2022-43421/index.md)
```

## Sources

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

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