CVE-2022-1963
First published: Fri Jul 01 2022(Updated: )
An issue has been discovered in GitLab CE/EE affecting all versions starting from 13.4 before 14.10.5, all versions starting from 15.0 before 15.0.4, all versions starting from 15.1 before 15.1.1. GitLab reveals if a user has enabled two-factor authentication on their account in the HTML source, to unauthenticated users.
Credit: cve@gitlab.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | >=13.4.0<14.10.5 | |
| GitLab | >=13.4.0<14.10.5 | |
| GitLab | >=15.0.0<15.0.4 | |
| GitLab | >=15.0.0<15.0.4 | |
| GitLab | =15.1.0 | |
| GitLab | =15.1.0 |
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-1963?
The severity of CVE-2022-1963 is classified as important due to its potential information disclosure.
How do I fix CVE-2022-1963?
To fix CVE-2022-1963, users should upgrade to GitLab versions 14.10.5, 15.0.4, or 15.1.1 and above.
What does CVE-2022-1963 affect?
CVE-2022-1963 affects all GitLab CE/EE versions starting from 13.4 before 14.10.5, 15.0 before 15.0.4, and 15.1 before 15.1.1.
What type of information is disclosed by CVE-2022-1963?
CVE-2022-1963 reveals whether a user has enabled two-factor authentication in the HTML source.
Who is impacted by CVE-2022-1963?
All users of affected GitLab CE and EE versions are potentially impacted by CVE-2022-1963.
- agent/type
- agent/references
- 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/13.4.0
- version/gitlab/15.0.0
- version/gitlab/15.1.0