What is the severity of CVE-2023-4812?

CVE-2023-4812 is considered a critical vulnerability that allows the bypassing of CODEOWNERS approval in GitLab.

How do I fix CVE-2023-4812?

To fix CVE-2023-4812, upgrade GitLab to version 16.6.4 or later, or to version 16.7.2 or later.

Which GitLab versions are affected by CVE-2023-4812?

CVE-2023-4812 affects GitLab versions from 15.3 before 16.5.6, from 16.6 before 16.6.4, and from 16.7 before 16.7.2.

What impact does CVE-2023-4812 have on GitLab users?

CVE-2023-4812 can lead to unauthorized changes in a project without proper CODEOWNERS approval, jeopardizing project integrity.

Is CVE-2023-4812 applicable to both GitLab Community and Enterprise editions?

Yes, CVE-2023-4812 affects both GitLab Community and Enterprise editions across specified vulnerable versions.

Vulnerability/
CVE-2023-4812

high

7.6

CWE

863

12/1/2024

14/11/2024

CVE-2023-4812: Incorrect Authorization in GitLab

First published: Fri Jan 12 2024(Updated: )

An issue has been discovered in GitLab EE affecting all versions starting from 15.3 before 16.5.6, all versions starting from 16.6 before 16.6.4, all versions starting from 16.7 before 16.7.2. The required CODEOWNERS approval could be bypassed by adding changes to a previously approved merge request.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=15.3.0<16.5.5
GitLab	>=15.3.0<16.5.5
GitLab	>=16.6.0<16.6.4
GitLab	>=16.6.0<16.6.4
GitLab	=16.7.0
GitLab	=16.7.1

Remedy

Upgrade to versions 16.7.2, 16.6.4, 16.5.6 or above.

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2023-4812?
CVE-2023-4812 is considered a critical vulnerability that allows the bypassing of CODEOWNERS approval in GitLab.
How do I fix CVE-2023-4812?
To fix CVE-2023-4812, upgrade GitLab to version 16.6.4 or later, or to version 16.7.2 or later.
Which GitLab versions are affected by CVE-2023-4812?
CVE-2023-4812 affects GitLab versions from 15.3 before 16.5.6, from 16.6 before 16.6.4, and from 16.7 before 16.7.2.
What impact does CVE-2023-4812 have on GitLab users?
CVE-2023-4812 can lead to unauthorized changes in a project without proper CODEOWNERS approval, jeopardizing project integrity.
Is CVE-2023-4812 applicable to both GitLab Community and Enterprise editions?
Yes, CVE-2023-4812 affects both GitLab Community and Enterprise editions across specified vulnerable versions.

agent/remedy
agent/author
agent/type
agent/first-publish-date
agent/severity
agent/description
collector/the-register
source/The Register
alias/CVE-2023-7028
agent/references
agent/event
agent/softwarecombine
agent/title
agent/weakness
collector/mitre-cve
source/MITRE
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/15.3.0
version/gitlab/16.6.0
version/gitlab/16.7.0
version/gitlab/16.7.1

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.