What is the severity of CVE-2022-3793?

CVE-2022-3793 has a medium severity rating due to improper authorization in GitLab allowing unauthorized data reading.

How do I fix CVE-2022-3793?

To fix CVE-2022-3793, upgrade GitLab to version 15.3.5, 15.4.4, or 15.5.2 or later.

Which versions of GitLab are affected by CVE-2022-3793?

CVE-2022-3793 affects GitLab CE/EE versions from 14.4 prior to 15.3.5, 15.4 prior to 15.4.4, and 15.5 prior to 15.5.2.

What type of issue is CVE-2022-3793 categorized as?

CVE-2022-3793 is categorized as an improper authorization issue.

Can CVE-2022-3793 lead to data exposure?

Yes, CVE-2022-3793 can allow an attacker to read sensitive variables from a GitLab CI/CD configuration file.

Vulnerability/
CVE-2022-3793

medium

5.3

9/11/2022

3/8/2024

CVE-2022-3793

First published: Wed Nov 09 2022(Updated: )

An improper authorization issue in GitLab CE/EE affecting all versions from 14.4 prior to 15.3.5, 15.4 prior to 15.4.4, and 15.5 prior to 15.5.2 allows an attacker to read variables set directly in a GitLab CI/CD configuration file they don't have access to.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=12.6.0<15.3.5
GitLab	>=12.6.0<15.3.5
GitLab	>=15.4.0<15.4.4
GitLab	>=15.4.0<15.4.4
GitLab	>=15.5.0<15.5.2
GitLab	>=15.5.0<15.5.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-3793?
CVE-2022-3793 has a medium severity rating due to improper authorization in GitLab allowing unauthorized data reading.
How do I fix CVE-2022-3793?
To fix CVE-2022-3793, upgrade GitLab to version 15.3.5, 15.4.4, or 15.5.2 or later.
Which versions of GitLab are affected by CVE-2022-3793?
CVE-2022-3793 affects GitLab CE/EE versions from 14.4 prior to 15.3.5, 15.4 prior to 15.4.4, and 15.5 prior to 15.5.2.
What type of issue is CVE-2022-3793 categorized as?
CVE-2022-3793 is categorized as an improper authorization issue.
Can CVE-2022-3793 lead to data exposure?
Yes, CVE-2022-3793 can allow an attacker to read sensitive variables from a GitLab CI/CD configuration file.

agent/references
agent/type
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/12.6.0
version/gitlab/15.4.0
version/gitlab/15.5.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-3793?
CVE-2022-3793 has a medium severity rating due to improper authorization in GitLab allowing unauthorized data reading.
How do I fix CVE-2022-3793?
To fix CVE-2022-3793, upgrade GitLab to version 15.3.5, 15.4.4, or 15.5.2 or later.
Which versions of GitLab are affected by CVE-2022-3793?
CVE-2022-3793 affects GitLab CE/EE versions from 14.4 prior to 15.3.5, 15.4 prior to 15.4.4, and 15.5 prior to 15.5.2.
What type of issue is CVE-2022-3793 categorized as?
CVE-2022-3793 is categorized as an improper authorization issue.
Can CVE-2022-3793 lead to data exposure?
Yes, CVE-2022-3793 can allow an attacker to read sensitive variables from a GitLab CI/CD configuration file.