What is the severity of CVE-2022-3325?

CVE-2022-3325 has a high severity rating due to improper access control in the GitLab API.

How do I fix CVE-2022-3325?

To fix CVE-2022-3325, upgrade to GitLab versions 15.2.5, 15.3.4, or 15.4.1 or later.

What versions are affected by CVE-2022-3325?

CVE-2022-3325 affects all GitLab CE/EE versions from 12.8 before 15.2.5, from 15.3 before 15.3.4, and from 15.4 before 15.4.1.

What kind of data can be accessed through CVE-2022-3325?

CVE-2022-3325 allows unauthorized users to edit approval rules via the GitLab API.

Is CVE-2022-3325 a local or remote vulnerability?

CVE-2022-3325 is a remote vulnerability that can be exploited through API calls.

Vulnerability/
CVE-2022-3325

medium

4.3

17/10/2022

3/8/2024

CVE-2022-3325

First published: Mon Oct 17 2022(Updated: )

Improper access control in the GitLab CE/EE API affecting all versions starting from 12.8 before 15.2.5, all versions starting from 15.3 before 15.3.4, all versions starting from 15.4 before 15.4.1. Allowed for editing the approval rules via the API by an unauthorised user.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=12.8.0<15.2.5
GitLab	>=12.8.0<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

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-3325?
CVE-2022-3325 has a high severity rating due to improper access control in the GitLab API.
How do I fix CVE-2022-3325?
To fix CVE-2022-3325, upgrade to GitLab versions 15.2.5, 15.3.4, or 15.4.1 or later.
What versions are affected by CVE-2022-3325?
CVE-2022-3325 affects all GitLab CE/EE versions from 12.8 before 15.2.5, from 15.3 before 15.3.4, and from 15.4 before 15.4.1.
What kind of data can be accessed through CVE-2022-3325?
CVE-2022-3325 allows unauthorized users to edit approval rules via the GitLab API.
Is CVE-2022-3325 a local or remote vulnerability?
CVE-2022-3325 is a remote vulnerability that can be exploited through API calls.

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

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-3325?
CVE-2022-3325 has a high severity rating due to improper access control in the GitLab API.
How do I fix CVE-2022-3325?
To fix CVE-2022-3325, upgrade to GitLab versions 15.2.5, 15.3.4, or 15.4.1 or later.
What versions are affected by CVE-2022-3325?
CVE-2022-3325 affects all GitLab CE/EE versions from 12.8 before 15.2.5, from 15.3 before 15.3.4, and from 15.4 before 15.4.1.
What kind of data can be accessed through CVE-2022-3325?
CVE-2022-3325 allows unauthorized users to edit approval rules via the GitLab API.
Is CVE-2022-3325 a local or remote vulnerability?
CVE-2022-3325 is a remote vulnerability that can be exploited through API calls.