Authenticated branch-prefix modification via unchecked REST authorization
Published Oct 19, 2022 · Updated Apr 22, 2025
Missing authorization in Enalean Tuleap 12.9.99.228 through 14.0.99.23 allows remote authenticated users to alter GitLab branch prefixes. The PATCH /gitlab_repositories/{id} handler accepts an integration visible to the caller and writes its branch-prefix setting without verifying Git administrator authority. A low-privileged account and visibility of an integrated GitLab repository are required; exploitation changes that integration's branch-reference behavior.
Summary
What happened
Missing authorization in Enalean Tuleap 12.9.99.228 through 14.0.99.23 allows remote authenticated users to alter GitLab branch prefixes. The PATCH /gitlab_repositories/{id} handler accepts an integration visible to the caller and writes its branch-prefix setting without verifying Git administrator authority. A low-privileged account and visibility of an integrated GitLab repository are required; exploitation changes that integration's branch-reference behavior.
The record
- CVE
- CVE-2022-39233
- Published
- Oct 19, 2022
- Updated
- Apr 22, 2025
- Vendor
- Enalean
- Product
- Tuleap
- Classifications
- CWE-862
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 19, 2022CVE publishedPublication date reported by the CVE source.
- Apr 22, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 12.9.99.228, < 14.0.99.24
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Branch-prefix REST request reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo