CVE-2022-1157: Low severity gitlab vulnerability
Published 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
Affected Software
6 affected components
GitLab GitLab<14.7.7
GitLab GitLab<14.7.7
GitLab GitLab>=14.8.0<14.8.5
GitLab GitLab>=14.8.0<14.8.5
GitLab GitLab>=14.9.0<14.9.2
GitLab GitLab>=14.9.0<14.9.2
Event History
Apr 11, 2022
CVE Published
via MITRE·07:38 PM
Data Sourced
via MITRE·07:38 PM
DescriptionSeverityWeakness
Frequently Asked Questions
1
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.
2
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.
3
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.
4
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.
5
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.