GitLab Enterprise Edition up to 18.0.5/18.1.3/18.2.1 IP Restrictions insufficient granularity of access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.5 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in GitLab Enterprise Edition up to 18.0.5/18.1.3/18.2.1. This impacts an unknown function of the component IP Restrictions Handler. The manipulation leads to insufficient granularity of access control. This vulnerability is documented as CVE-2025-2498. The attack can be initiated remotely. There is not any exploit available. You should upgrade the affected component.
Details
A vulnerability was found in GitLab Enterprise Edition up to 18.0.5/18.1.3/18.2.1. It has been rated as problematic. This issue affects some unknown functionality of the component IP Restrictions Handler. The manipulation with an unknown input leads to a insufficient granularity of access control vulnerability. Using CWE to declare the problem leads to CWE-1220. The product implements access controls via a policy or other feature with the intention to disable or restrict accesses (reads and/or writes) to assets in a system from untrusted agents. However, implemented access controls lack required granularity, which renders the control policy too broad because it allows accesses from unauthorized agents to the security-sensitive assets. Impacted is confidentiality. The summary by CVE is:
An improper access control in Gitlab EE affecting all versions from 12.0 prior to 18.0.6, 18.1 prior to 18.1.4, and 18.2 prior to 18.2.2 that under certain conditions could have allowed users to view assigned issues from restricted groups by bypassing IP restrictions.
The weakness was released by rogerace as 525515. The advisory is shared at gitlab.com. The identification of this vulnerability is CVE-2025-2498 since 03/18/2025. The exploitation is known to be difficult. The attack may be initiated remotely. Neither technical details nor an exploit are publicly available.
Upgrading to version 18.0.6, 18.1.4 or 18.2.2 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2025-1816). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- Open Source GitLab
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://gitlab.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.5VulDB Meta Temp Score: 3.5
VulDB Base Score: 3.1
VulDB Temp Score: 3.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 4.3
NVD Vector: 🔒
CNA Base Score: 3.1
CNA Vector (GitLab): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Insufficient granularity of access controlCWE: CWE-1220 / CWE-284 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Enterprise Edition 18.0.6/18.1.4/18.2.2
Timeline
03/18/2025 CVE reserved08/13/2025 Advisory disclosed
08/13/2025 VulDB entry created
08/16/2025 VulDB entry last update
Sources
Vendor: gitlab.comAdvisory: 525515
Researcher: rogerace
Status: Confirmed
CVE: CVE-2025-2498 (🔒)
GCVE (CVE): GCVE-0-2025-2498
GCVE (VulDB): GCVE-100-320021
CERT Bund: WID-SEC-2025-1816 - GitLab: Mehrere Schwachstellen
Entry
Created: 08/13/2025 20:45Updated: 08/16/2025 04:28
Changes: 08/13/2025 20:45 (66), 08/13/2025 21:25 (7), 08/14/2025 16:51 (1), 08/16/2025 04:28 (11)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.