CVE-2022-3330
First published: Mon Oct 17 2022(Updated: )
It was possible for a guest user to read a todo targeting an inaccessible note in Gitlab CE/EE affecting all versions from 15.0 prior to 15.2.5, 15.3 prior to 15.3.4, and 15.4 prior to 15.4.1.
Credit: cve@gitlab.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | >=15.0.0<15.2.5 | |
| GitLab | >=15.0.0<15.2.5 | |
| GitLab | >=15.3<15.3.4 | |
| GitLab | >=15.3<15.3.4 | |
| GitLab | >=15.4<15.4.1 | |
| GitLab | >=15.4<15.4.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2022-3330?
CVE-2022-3330 is considered a medium severity vulnerability due to the potential exposure of sensitive note information to guest users.
What versions are affected by CVE-2022-3330?
CVE-2022-3330 affects all versions of GitLab CE/EE from 15.0 prior to 15.2.5, 15.3 prior to 15.3.4, and 15.4 prior to 15.4.1.
How do I fix CVE-2022-3330?
To fix CVE-2022-3330, upgrade GitLab to version 15.2.5 or later, 15.3.4 or later, or 15.4.1 or later.
What impact does CVE-2022-3330 have on data security?
CVE-2022-3330 allows guest users to read todo items that may be associated with private notes, potentially leading to unauthorized data exposure.
Who should be concerned about CVE-2022-3330?
Organizations using affected versions of GitLab CE/EE should be concerned about CVE-2022-3330 and should take immediate action to upgrade.
- agent/references
- agent/type
- agent/author
- agent/softwarecombine
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/severity
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/gitlab
- canonical/gitlab
- version/gitlab/15.0.0
- version/gitlab/15.3
- version/gitlab/15.4