CVE-2022-4365: Medium severity gitlab vulnerability
An issue has been discovered in GitLab CE/EE affecting all versions starting from 11.8 before 15.5.7, all versions starting from 15.6 before 15.6.4, all versions starting from 15.7 before 15.7.2. A malicious Maintainer can leak the sentry token by changing the configured URL in the Sentry error tracking settings page.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2022-4365?
CVE-2022-4365 is classified as a critical vulnerability due to the potential for a malicious maintainer to leak sensitive Sentry tokens.
How do I fix CVE-2022-4365?
To fix CVE-2022-4365, upgrade GitLab to version 15.5.7 or later, 15.6.4 or later, or 15.7.2 or later depending on your current version.
Who is affected by CVE-2022-4365?
CVE-2022-4365 affects all versions of GitLab starting from 11.8 to 15.5.7, 15.6 from 15.6.0 to 15.6.4, and 15.7 from 15.7.0 to 15.7.2.
What actions should be taken if CVE-2022-4365 is exploited?
If CVE-2022-4365 is exploited, it's crucial to reset affected Sentry tokens and apply the necessary GitLab security updates immediately.
Can CVE-2022-4365 affect both GitLab CE and EE versions?
Yes, CVE-2022-4365 impacts both GitLab Community Edition (CE) and Enterprise Edition (EE) across the specified version ranges.