CVE-2022-3325: Medium severity gitlab vulnerability
Published 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.
Affected Software
6 affected components
GitLab GitLab>=12.8.0<15.2.5
GitLab GitLab>=12.8.0<15.2.5
GitLab GitLab>=15.3<15.3.4
GitLab GitLab>=15.3<15.3.4
GitLab GitLab>=15.4<15.4.1
GitLab GitLab>=15.4<15.4.1
Event History
Oct 17, 2022
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionSeverityWeakness
Frequently Asked Questions
1
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.
2
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.
3
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.
4
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.
5
Is CVE-2022-3325 a local or remote vulnerability?
CVE-2022-3325 is a remote vulnerability that can be exploited through API calls.