An information disclosure issue in Gitlab CE/EE affecting all versions from 13.6 prior to 15.11.10, all versions from 16.0 prior to 16.0.6, all versions from 16.1 prior to 16.1.1, resulted in the Sidekiq log including webhook tokens when the log format was set to `default`.
This vulnerability carries a LOW severity rating with a CVSS v3.1 score of 3.9, requiring local system access to exploit but requires specific conditions to be met without requiring user interaction . The vulnerability impacts limited data confidentiality, limited integrity, for affected systems. Impacting 1 product from gitlab organizations running these solutions should prioritize assessment and patching.
Reported in 2023, this vulnerability emerged during an era marked by increased sophistication in supply chain attacks, cloud infrastructure vulnerabilities, and software-as-a-service (SaaS) security challenges. Security practices during this period emphasized zero-trust architectures, container security, and API protection.
2023-07-13T03:15:10.280
2024-11-21T08:17:06.270
Modified
CVSSv3.1: 3.9 (LOW)
| Type | Vendor | Product | Version/Range | Vulnerable? |
|---|---|---|---|---|
| Application | gitlab | gitlab | < 15.11.10 | Yes |
| Application | gitlab | gitlab | < 15.11.10 | Yes |
| Application | gitlab | gitlab | < 16.0.6 | Yes |
| Application | gitlab | gitlab | < 16.0.6 | Yes |
| Application | gitlab | gitlab | < 16.1.1 | Yes |
| Application | gitlab | gitlab | < 16.1.1 | Yes |
SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For gitlab's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.