What is the severity of CVE-2024-4784?

CVE-2024-4784 has a high severity rating due to the potential for unauthorized policy approvals.

How do I fix CVE-2024-4784?

To fix CVE-2024-4784, upgrade your GitLab EE installation to version 17.0.6, 17.1.4, or 17.2.2 or later.

What products are affected by CVE-2024-4784?

CVE-2024-4784 affects GitLab EE versions from 16.7 up to but not including 17.0.6, and versions from 17.1 up to but not including 17.1.4 and from 17.2 up to but not including 17.2.2.

Does CVE-2024-4784 allow for remote exploitation?

CVE-2024-4784 does not involve remote exploitation as it requires authenticated access to GitLab EE.

What impact does CVE-2024-4784 have on GitLab EE users?

CVE-2024-4784 could lead to significant security risks by allowing users to approve policies without proper password verification.

Vulnerability/
CVE-2024-4784

medium

5.4

CWE

305 287

8/8/2024

29/8/2024

CVE-2024-4784: Authentication Bypass by Primary Weakness in GitLab

First published: Thu Aug 08 2024(Updated: )

An issue was discovered in GitLab EE starting from version 16.7 before 17.0.6, version 17.1 before 17.1.4 and 17.2 before 17.2.2 that allowed bypassing the password re-entry requirement to approve a policy.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=16.7.0<17.0.6
GitLab	>=17.1.0<17.1.4

Remedy

Upgrade to versions 17.2.2, 17.1.4, 17.0.6 or above.

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2024-4784?
CVE-2024-4784 has a high severity rating due to the potential for unauthorized policy approvals.
How do I fix CVE-2024-4784?
To fix CVE-2024-4784, upgrade your GitLab EE installation to version 17.0.6, 17.1.4, or 17.2.2 or later.
What products are affected by CVE-2024-4784?
CVE-2024-4784 affects GitLab EE versions from 16.7 up to but not including 17.0.6, and versions from 17.1 up to but not including 17.1.4 and from 17.2 up to but not including 17.2.2.
Does CVE-2024-4784 allow for remote exploitation?
CVE-2024-4784 does not involve remote exploitation as it requires authenticated access to GitLab EE.
What impact does CVE-2024-4784 have on GitLab EE users?
CVE-2024-4784 could lead to significant security risks by allowing users to approve policies without proper password verification.

agent/author
agent/references
agent/type
agent/description
agent/title
agent/remedy
agent/first-publish-date
agent/weakness
agent/severity
agent/softwarecombine
agent/event
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/16.7.0
version/gitlab/17.1.0
version/gitlab/17.2.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.