CVE-2022-3030
First published: Mon Oct 17 2022(Updated: )
An improper access control issue in GitLab CE/EE affecting all versions starting before 15.1.6, all versions from 15.2 before 15.2.4, all versions from 15.3 before 15.3.2 allows disclosure of pipeline status to unauthorized users.
Credit: cve@gitlab.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | <15.1.6 | |
| GitLab | <15.1.6 | |
| GitLab | >=15.2<15.2.4 | |
| GitLab | >=15.2<15.2.4 | |
| GitLab | >=15.3<15.3.2 | |
| GitLab | >=15.3<15.3.2 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2022-3030?
CVE-2022-3030 is classified as a medium severity vulnerability due to improper access control leading to disclosure of sensitive information.
How do I fix CVE-2022-3030?
To fix CVE-2022-3030, update GitLab to version 15.1.6 or later, 15.2.4 or later, or 15.3.2 or later.
What types of users are affected by CVE-2022-3030?
CVE-2022-3030 affects unauthorized users who may gain access to pipeline status information.
Which versions of GitLab are impacted by CVE-2022-3030?
CVE-2022-3030 affects all GitLab CE/EE versions prior to 15.1.6, between 15.2 and 15.2.4, and between 15.3 and 15.3.2.
What is an improper access control vulnerability in the context of CVE-2022-3030?
In CVE-2022-3030, improper access control allows unauthorized users to view sensitive pipeline status details.
- agent/type
- agent/references
- agent/author
- agent/softwarecombine
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/last-modified-date
- agent/event
- agent/first-publish-date
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/gitlab
- canonical/gitlab
- version/gitlab/15.2
- version/gitlab/15.3