Sensitive URL disclosure via unsanitized exception logging
Published Apr 11, 2022 · Updated Aug 2, 2024
Sensitive information exposure in GitLab CE/EE before 14.7.7, 14.8 before 14.8.5, and 14.9 before 14.9.2 lets attackers place URL secrets in logs. The URI exception path passes URI::InvalidURIError messages to application logs without redacting credentials embedded in the rejected URL. Exploitation requires high-privilege access and user interaction with a malformed integration URL; resulting exposure is limited to sensitive values readable from server logs.
Summary
What happened
Sensitive information exposure in GitLab CE/EE before 14.7.7, 14.8 before 14.8.5, and 14.9 before 14.9.2 lets attackers place URL secrets in logs. The URI exception path passes URI::InvalidURIError messages to application logs without redacting credentials embedded in the rejected URL. Exploitation requires high-privilege access and user interaction with a malformed integration URL; resulting exposure is limited to sensitive values readable from server logs.
The record
- CVE
- CVE-2022-1157
- Published
- Apr 11, 2022
- Updated
- Aug 2, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-532
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 11, 2022CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=<14.7.7
- Affected versionversion=>=14.8, <14.8.5
- Affected versionversion=>=14.9, <14.9.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo