First published: Wed Jul 17 2024(Updated: )
An issue was discovered in GitLab CE/EE affecting all versions starting from 11.8 prior to 16.11.6, starting from 17.0 prior to 17.0.4, and starting from 17.1 prior to 17.1.2 where it was possible to upload an NPM package with conflicting package data.
Credit: cve@gitlab.com
Affected Software | Affected Version | How to fix |
---|---|---|
GitLab | >=11.8.0<16.11.6 | |
GitLab | >=11.8.0<16.11.6 | |
GitLab | >=17.0.0<17.0.4 | |
GitLab | >=17.0.0<17.0.4 | |
GitLab | >=17.1.0<17.1.2 | |
GitLab | >=17.1.0<17.1.2 |
Upgrade to versions 16.11.6, 17.0.4, 17.1.2 or above.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-6595 has been classified as a moderate severity vulnerability.
To fix CVE-2024-6595, upgrade GitLab to version 16.11.6, 17.0.4, or 17.1.2 or later.
CVE-2024-6595 affects all GitLab CE and EE versions from 11.8 prior to 16.11.6, from 17.0 prior to 17.0.4, and from 17.1 prior to 17.1.2.
CVE-2024-6595 is a vulnerability that allows the upload of an NPM package with conflicting package data.
Yes, CVE-2024-6595 affects both community and enterprise editions of GitLab.