Email-address disclosure via unredacted webhook logs
Published Oct 17, 2022 · Updated May 13, 2025
Information exposure in GitLab EE allows remote authenticated users to read private email addresses from integration webhook logs. The webhook log detail view retains and renders commit-author values in request data without redacting strings that contain email addresses. A user must be able to test an integration and open its webhook log details; exposure is limited to addresses present in logged payloads.
Summary
What happened
Information exposure in GitLab EE allows remote authenticated users to read private email addresses from integration webhook logs. The webhook log detail view retains and renders commit-author values in request data without redacting strings that contain email addresses. A user must be able to test an integration and open its webhook log details; exposure is limited to addresses present in logged payloads.
The record
- CVE
- CVE-2022-3293
- Published
- Oct 17, 2022
- Updated
- May 13, 2025
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 17, 2022CVE publishedPublication date reported by the CVE source.
- May 13, 2025Record 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=>=15.3, <15.3.4
- Affected versionversion=>=15.4, <15.4.1
- Affected versionversion=>=9.3, <15.2.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
No sourced classifications are available.
Public exploit references
- GitLab issue 369008 reproduction procedureproof of concept · demonstrated
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