MEDIUM

CVE-2023-2190

Gitlab GitLab 2023-07-13 CVSS v3.1
CVSS
6.5

Description

An issue has been discovered in GitLab CE/EE affecting all versions starting from 13.10 before 15.11.10, all versions starting from 16.0 before 16.0.6, all versions starting from 16.1 before 16.1.1. It may be possible for users to view new commits to private projects in a fork created while the project was public.

Summary dbcve.org

This is an authorization bypass vulnerability in GitLab where forks created while a project was public may continue exposing commits even after the original project becomes private. When a user creates a fork from a public project and the parent project is later made private, the fork relationship can still be exploited to view commits that should no longer be accessible.

Mitigation

Upgrade GitLab to version 15.11.10, 16.0.6, 16.1.1 or later. Additionally, audit fork relationships for projects that transitioned from public to private and review access logs for any unauthorized commit viewing.

Weakness (CWE)

CWE-639 Authorization Bypass (IDOR)

EPSS Score

0.66%
Probability of exploitation in next 30 days
50.2th percentile

References

View on dbcve.org
Base CVE data derived from NVD (public domain). Enrichment by dbcve.org (CC-BY-4.0). Fetched via API.
Back to CVE