CVE-2022-1157
First published: Mon Apr 11 2022(Updated: )
Missing sanitization of logged exception messages in all versions prior to 14.7.7, 14.8 prior to 14.8.5, and 14.9 prior to 14.9.2 of GitLab CE/EE causes potential sensitive values in invalid URLs to be logged
Credit: cve@gitlab.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | <14.7.7 | |
| GitLab | <14.7.7 | |
| GitLab | >=14.8.0<14.8.5 | |
| GitLab | >=14.8.0<14.8.5 | |
| GitLab | >=14.9.0<14.9.2 | |
| GitLab | >=14.9.0<14.9.2 |
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-1157?
CVE-2022-1157 is classified as a high severity vulnerability due to the potential exposure of sensitive information.
How do I fix CVE-2022-1157?
To remediate CVE-2022-1157, upgrade to GitLab version 14.7.7, 14.8.5, or 14.9.2 or later.
What versions of GitLab are affected by CVE-2022-1157?
CVE-2022-1157 affects all versions of GitLab prior to 14.7.7, 14.8 prior to 14.8.5, and 14.9 prior to 14.9.2.
What type of information does CVE-2022-1157 potentially expose?
CVE-2022-1157 can potentially expose sensitive values found in invalid URLs logged by the application.
Is CVE-2022-1157 related to logging vulnerabilities?
Yes, CVE-2022-1157 involves missing sanitization of logged exception messages, which can lead to sensitive data exposure.
- agent/type
- agent/references
- agent/weakness
- agent/author
- agent/softwarecombine
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/last-modified-date
- agent/event
- agent/first-publish-date
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/gitlab
- canonical/gitlab
- version/gitlab/14.8.0
- version/gitlab/14.9.0