# CVE-2022-39233: Tuleap subject to Missing Authorization allowing for branch prefix modification

> Authenticated users can modify GitLab repository branch prefixes via a REST endpoint, bypassing restrictions intended for Git administrators.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Oct 2022
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-3884-972x-3ccq

## What is CVE-2022-39233?

CVE-2022-39233 is a medium-severity missing authorization vulnerability in Enalean Tuleap, published on 19 Oct 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Tuleap is a Free & Open Source Suite to improve management of software developments and collaboration. In versions 12.9.99.228 and above, prior to 14.0.99.24, authorizations are not properly verified when updating the branch prefix used by the GitLab repository integration. Authenticated users can change the branch prefix of any of the GitLab repository integration they can see vie the REST endpoint `PATCH /gitlab_repositories/{id}`. This action should be restricted to Git administrators. This issue is patched in Tuleap Community Edition 14.0.99.24 and Tuleap Enterprise Edition 14.0-3. There are no known workarounds.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Enalean Tuleap.

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

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

## Is CVE-2022-39233 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-39233 exists.

## Other vulnerabilities in Enalean Tuleap

- [CVE-2018-17298](https://insights.sbomify.com/CVE-2018-17298/): Business logic in n/a (critical 9.8)
- [CVE-2018-7538](https://insights.sbomify.com/CVE-2018-7538/): SQL injection in n/a (critical 9.8)
- [CVE-2014-7178](https://insights.sbomify.com/CVE-2014-7178/): Command injection in n/a (critical 9.3)
- [CVE-2021-43806](https://insights.sbomify.com/CVE-2021-43806/): SQL injection in Tuleap (high 8.8)
- [CVE-2021-41154](https://insights.sbomify.com/CVE-2021-41154/): SQL injection in the "SVN core" commits browser (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-39233 is a medium-severity missing authorization vulnerability in Enalean Tuleap, published on 19 Oct 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-39233 exists.

Affected product: Enalean Tuleap. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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