CVE-2022-3279
First published: Mon Oct 17 2022(Updated: )
An unhandled exception in job log parsing in GitLab CE/EE affecting all versions prior to 15.2.5, 15.3 prior to 15.3.4, and 15.4 prior to 15.4.1 allows an attacker to prevent access to job logs
Credit: cve@gitlab.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | <15.2.5 | |
| GitLab | <15.2.5 | |
| GitLab | >=15.3<15.3.4 | |
| GitLab | >=15.3<15.3.4 | |
| GitLab | >=15.4<15.4.1 | |
| GitLab | >=15.4<15.4.1 |
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-3279?
CVE-2022-3279 is classified as a medium severity vulnerability.
How do I fix CVE-2022-3279?
To fix CVE-2022-3279, you should upgrade GitLab to version 15.2.5 or later, or to version 15.3.4 or later, or to version 15.4.1 or later.
What effect does CVE-2022-3279 have on GitLab installations?
CVE-2022-3279 allows an attacker to prevent access to job logs in affected versions of GitLab.
Which versions of GitLab are affected by CVE-2022-3279?
CVE-2022-3279 affects all versions of GitLab prior to 15.2.5, 15.3 prior to 15.3.4, and 15.4 prior to 15.4.1.
Are both GitLab CE and EE impacted by CVE-2022-3279?
Yes, both GitLab Community Edition (CE) and Enterprise Edition (EE) are impacted by CVE-2022-3279.
- agent/type
- agent/references
- agent/author
- agent/weakness
- 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.3
- version/gitlab/15.4