GitLab: Improper Privilege Management
CVE-2022-2498 is a high-severity improper privilege management vulnerability in GitLab, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected GitLab versions: >=12.8, <15.0.5; >=15.1, <15.1.4; >=15.2, <15.2.1. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.87% chance of exploitation within 30 days, higher than 59% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of GitLab you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on gitlab.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| GitLab | GitLab | >=12.8, <15.0.5; >=15.1, <15.1.4; >=15.2, <15.2.1 | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 6.4 | Medium | CNA (gitlab.com) |
| CVSS 3.1 | 7.5 | High | NVD |
Official description
An issue in pipeline subscriptions in GitLab EE affecting all versions from 12.8 prior to 15.0.5, 15.1 prior to 15.1.4, and 15.2 prior to 15.2.1 triggered new pipelines with the person who created the tag as the pipeline creator instead of the subscription's author.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Privilege Management
The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.
How developers prevent this class of flaw
- Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
- Follow the principle of least privilege when assigning access rights to entities in a software system.
- Consider following the principle of separation of privilege. Require multiple conditions to be met before permitting access to a system resource.
More Improper Privilege Management vulnerabilities (CWE-269)
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- hackerone.com/reports/966824Permissions Required, Third Party Advisory
Other vulnerabilities in GitLab
- 7.1 High severity
- 8.2 High severity
- 7.5 High severity
- 10.0 Critical severity
- 10.0 Critical severity
- 7.3 High severity
Recent Improper Privilege Management vulnerabilities
- 7.8 High severity
- 9.1 Critical severity
- 9.8 Critical severity
- 8.8 High severity
- 8.1 High severity
- 7.1 High severity
Spotted an error? Tell us.