Skip to content

GitLab repository branch prefix can be updated by any user

Moderate
LeSuisse published GHSA-3884-972x-3ccq Oct 17, 2022

Package

Tuleap Community Edition (tuleap)

Affected versions

>= 12.9.99.228 && < 14.0.99.24

Patched versions

14.0.99.24
Tuleap Enterprise Edition (tuleap)
>= 14.0 && < 14.0-3
>= 12.10 && < 13.12-6
14.0-3
13.12-6

Description

Authorizations are not properly verified when updating the branch prefix used by the GitLab repository integration.

Impact

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.

Patches

The following versions contain the fix:

  • Tuleap Community Edition 14.0.99.24
  • Tuleap Enterprise Edition 14.0-3
  • Tuleap Enterprise Edition 13.2-6

For more information

If you have any questions or comments about this advisory, reach out to us via the contact information provided on the Tuleap.org security page.

References

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

CVE ID

CVE-2022-39233

Weaknesses