What is the severity of CVE-2023-3907?

CVE-2023-3907 has been rated as a high severity vulnerability due to its potential for privilege escalation.

How do I fix CVE-2023-3907?

To mitigate CVE-2023-3907, update GitLab EE to version 16.4.4 or later, 16.5.4 or later, or 16.6.2 or later.

What versions are affected by CVE-2023-3907?

CVE-2023-3907 affects GitLab EE versions from 16.0 prior to 16.4.4, 16.5 prior to 16.5.4, and 16.6 prior to 16.6.2.

Who is impacted by CVE-2023-3907?

CVE-2023-3907 allows project Maintainers in GitLab to escalate their roles to Owner, impacting project security and access controls.

What action should I take after identifying CVE-2023-3907 in my GitLab instance?

After identifying CVE-2023-3907, prioritize updating to a fixed version and review project access tokens and permissions.

Vulnerability/
CVE-2023-3907

high

8.8

CWE

286

17/12/2023

8/10/2024

CVE-2023-3907: Improper User Management in GitLab

First published: Sun Dec 17 2023(Updated: )

A privilege escalation vulnerability in GitLab EE affecting all versions from 16.0 prior to 16.4.4, 16.5 prior to 16.5.4, and 16.6 prior to 16.6.2 allows a project Maintainer to use a Project Access Token to escalate their role to Owner

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=16.0.0<16.4.4
GitLab	>=16.5<16.5.4
GitLab	>=16.6<16.6.2

Remedy

Upgrade to version 16.4.4, 16.5.4 or 16.6.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2023-3907?
CVE-2023-3907 has been rated as a high severity vulnerability due to its potential for privilege escalation.
How do I fix CVE-2023-3907?
To mitigate CVE-2023-3907, update GitLab EE to version 16.4.4 or later, 16.5.4 or later, or 16.6.2 or later.
What versions are affected by CVE-2023-3907?
CVE-2023-3907 affects GitLab EE versions from 16.0 prior to 16.4.4, 16.5 prior to 16.5.4, and 16.6 prior to 16.6.2.
Who is impacted by CVE-2023-3907?
CVE-2023-3907 allows project Maintainers in GitLab to escalate their roles to Owner, impacting project security and access controls.
What action should I take after identifying CVE-2023-3907 in my GitLab instance?
After identifying CVE-2023-3907, prioritize updating to a fixed version and review project access tokens and permissions.

agent/references
agent/type
agent/event
agent/first-publish-date
agent/remedy
agent/author
agent/severity
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
agent/title
agent/weakness
agent/last-modified-date
agent/source
agent/tags
collector/nvd-api
source/NVD
agent/software-canonical-lookup
agent/software-canonical-lookup-request
vendor/gitlab
canonical/gitlab
version/gitlab/16.0.0
version/gitlab/16.5
version/gitlab/16.6

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.