CVE-2023-0508
Gitlab 15.4.0 – 15.10.8
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:NSummary
CVE-2023-0508 is a low-severity HTTP Request/Response Splitting (CWE-113) vulnerability in Gitlab Gitlab. Its CVSS base score is 3.1 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked in the top 48% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
An issue has been discovered in GitLab CE/EE affecting all versions starting from 15.4 before 15.10.8, all versions starting from 15.11 before 15.11.7, and all versions starting from 16.0 before 16.0.2. The vulnerability is an open redirection that can be triggered via HTTP response splitting in the NPM package API, corresponding to CWE-113. It carries a CVSS 3.1 score of 3.1 reflecting network attack vector, high attack complexity, no required privileges, and required user interaction.
An attacker without authentication can exploit the flaw by crafting a request to the NPM package API that causes a split response, resulting in redirection to an arbitrary destination. Successful exploitation yields limited integrity impact while leaving confidentiality and availability unaffected.
GitLab advisories and the associated issue tracker entries direct administrators to upgrade to the fixed releases 15.10.8, 15.11.7, or 16.0.2. The EPSS score remains flat at 0.0592 with no material increase after disclosure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-12555
Vulnerability Data
An issue has been discovered in GitLab CE/EE affecting all versions starting from 15.4 before 15.10.8, all versions starting from 15.11 before 15.11.7, all versions starting from 16.0 before 16.0.2. Open redirection was possible via HTTP response splitting in the…
more
NPM package API.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V3.4.2V4.1.3V1.3.6V4.2.3
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require input sanitization and header handling that prevent CRLF injection.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development and acceptance can detect CRLF injection flaws before deployment.
Secure development lifecycle mandates input validation and output encoding that directly prevents CRLF injection into HTTP headers.
Application security requirements explicitly call for controls against injection flaws including HTTP header manipulation.
Secure architecture principles reduce the likelihood of header-splitting vulnerabilities through proper component isolation.
Secure coding standards require neutralization of CRLF sequences before inclusion in HTTP headers.
Logging of HTTP traffic can record header-splitting attempts, aiding detection and forensics.