GitLab: Files or Directories Accessible to External Parties
CVE-2022-0244 is a high-severity files or directories accessible to external parties 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: >=14.6, <14.6.2; >=14.5, <14.5.3. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 1.79% chance of exploitation within 30 days, higher than 79% 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
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
- HighAll data handled by the component can be read.
- Integrity
- NoneNothing can be modified.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 8.6 | High | CNA (gitlab.com) |
| CVSS 3.1 | 7.5 | High | NVD |
| CVSS 2.0 | 5.0 | Medium | NVD |
Official description
An issue has been discovered in GitLab CE/EE affecting all versions starting with 14.5. Arbitrary file read was possible by importing a group was due to incorrect handling of file.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Files or Directories Accessible to External Parties
The product makes files or directories accessible to unauthorized actors, even though they should not be.
How developers prevent this class of flaw
- When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to disable public access.
More Files or Directories Accessible to External Parties vulnerabilities (CWE-552)
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- hackerone.com/reports/1439593Permissions 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 Files or Directories Accessible to External Parties vulnerabilities
- 7.5 High severity
Apache Flink Improper Access Control Exploited
- 7.8 High severity
Roundcube Webmail File Disclosure Exploited
- 5.5 Medium severity
ImageMagick Arbitrary File Deletion Exploited
Spotted an error? Tell us.