What is the severity of CVE-2022-1124?

CVE-2022-1124 is considered a high severity vulnerability due to improper authorization allowing unauthorized access to sensitive data.

How do I fix CVE-2022-1124?

To fix CVE-2022-1124, upgrade GitLab to the latest version 14.8.6 or any version from 14.9.4 onwards.

Who is affected by CVE-2022-1124?

CVE-2022-1124 affects all GitLab CE/EE versions prior to 14.8.6, versions from 14.9.0 to just below 14.9.4, and exactly version 14.10.0.

What does CVE-2022-1124 exploit?

CVE-2022-1124 exploits an improper authorization issue that allows Guest project members to access trace logs of jobs.

What are the potential consequences of CVE-2022-1124?

The potential consequences of CVE-2022-1124 include unauthorized exposure of sensitive job trace logs to Guest project members.

Vulnerability/
CVE-2022-1124

medium

4.3

CWE

863

11/5/2022

2/8/2024

CVE-2022-1124

First published: Wed May 11 2022(Updated: )

An improper authorization issue has been discovered in GitLab CE/EE affecting all versions prior to 14.8.6, all versions from 14.9.0 prior to 14.9.4, and 14.10.0, allowing Guest project members to access trace log of jobs when it is enabled

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	<14.8.6
GitLab	<14.8.6
GitLab	>=14.9.0<14.9.4
GitLab	>=14.9.0<14.9.4
GitLab	=14.10.0
GitLab	=14.10.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-1124?
CVE-2022-1124 is considered a high severity vulnerability due to improper authorization allowing unauthorized access to sensitive data.
How do I fix CVE-2022-1124?
To fix CVE-2022-1124, upgrade GitLab to the latest version 14.8.6 or any version from 14.9.4 onwards.
Who is affected by CVE-2022-1124?
CVE-2022-1124 affects all GitLab CE/EE versions prior to 14.8.6, versions from 14.9.0 to just below 14.9.4, and exactly version 14.10.0.
What does CVE-2022-1124 exploit?
CVE-2022-1124 exploits an improper authorization issue that allows Guest project members to access trace logs of jobs.
What are the potential consequences of CVE-2022-1124?
The potential consequences of CVE-2022-1124 include unauthorized exposure of sensitive job trace logs to Guest project members.

agent/type
agent/references
agent/weakness
agent/author
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
agent/severity
agent/last-modified-date
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/gitlab
canonical/gitlab
version/gitlab/14.9.0
version/gitlab/14.10.0

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2022-1124?
CVE-2022-1124 is considered a high severity vulnerability due to improper authorization allowing unauthorized access to sensitive data.
How do I fix CVE-2022-1124?
To fix CVE-2022-1124, upgrade GitLab to the latest version 14.8.6 or any version from 14.9.4 onwards.
Who is affected by CVE-2022-1124?
CVE-2022-1124 affects all GitLab CE/EE versions prior to 14.8.6, versions from 14.9.0 to just below 14.9.4, and exactly version 14.10.0.
What does CVE-2022-1124 exploit?
CVE-2022-1124 exploits an improper authorization issue that allows Guest project members to access trace logs of jobs.
What are the potential consequences of CVE-2022-1124?
The potential consequences of CVE-2022-1124 include unauthorized exposure of sensitive job trace logs to Guest project members.