What is the severity of CVE-2024-3959?

CVE-2024-3959 is classified as a high-severity vulnerability due to the exposure of private job artifacts.

How do I fix CVE-2024-3959?

To fix CVE-2024-3959, upgrade GitLab to version 16.11.5 or 17.0.3 and above, or 17.1.1 or later.

What versions of GitLab are affected by CVE-2024-3959?

CVE-2024-3959 affects GitLab versions from 16.7 up to 16.11.5, 17.0 up to 17.0.3, and 17.1.0.

What is the impact of CVE-2024-3959?

The impact of CVE-2024-3959 allows unauthorized access to private job artifacts by any user within the system.

Is CVE-2024-3959 applicable to both Community and Enterprise editions?

Yes, CVE-2024-3959 affects both GitLab Community and Enterprise editions.

Vulnerability/
CVE-2024-3959

medium

6.5

CWE

285

26/6/2024

29/8/2024

CVE-2024-3959: Improper Authorization in GitLab

First published: Wed Jun 26 2024(Updated: )

An issue was discovered in GitLab CE/EE affecting all versions starting from 16.7 prior to 16.11.5, starting from 17.0 prior to 17.0.3, and starting from 17.1 prior to 17.1.1, which allows private job artifacts can be accessed by any user.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=16.7.0<16.11.5
GitLab	>=16.7.0<16.11.5
GitLab	>=17.0.0<17.0.3
GitLab	>=17.0.0<17.0.3
GitLab	=17.1.0
GitLab	=17.1.0

Remedy

Upgrade to versions 17.1.1, 17.0.3, 16.11.5 or above.

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2024-3959?
CVE-2024-3959 is classified as a high-severity vulnerability due to the exposure of private job artifacts.
How do I fix CVE-2024-3959?
To fix CVE-2024-3959, upgrade GitLab to version 16.11.5 or 17.0.3 and above, or 17.1.1 or later.
What versions of GitLab are affected by CVE-2024-3959?
CVE-2024-3959 affects GitLab versions from 16.7 up to 16.11.5, 17.0 up to 17.0.3, and 17.1.0.
What is the impact of CVE-2024-3959?
The impact of CVE-2024-3959 allows unauthorized access to private job artifacts by any user within the system.
Is CVE-2024-3959 applicable to both Community and Enterprise editions?
Yes, CVE-2024-3959 affects both GitLab Community and Enterprise editions.

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

Frequently Asked Questions

What is the severity of CVE-2024-3959?
CVE-2024-3959 is classified as a high-severity vulnerability due to the exposure of private job artifacts.
How do I fix CVE-2024-3959?
To fix CVE-2024-3959, upgrade GitLab to version 16.11.5 or 17.0.3 and above, or 17.1.1 or later.
What versions of GitLab are affected by CVE-2024-3959?
CVE-2024-3959 affects GitLab versions from 16.7 up to 16.11.5, 17.0 up to 17.0.3, and 17.1.0.
What is the impact of CVE-2024-3959?
The impact of CVE-2024-3959 allows unauthorized access to private job artifacts by any user within the system.
Is CVE-2024-3959 applicable to both Community and Enterprise editions?
Yes, CVE-2024-3959 affects both GitLab Community and Enterprise editions.