Cyber Resilience

CVE-2023-3906

Gitlab 12.3 – 16.2.8

Published
29 September 2023
Modified
05 May 2025
Patch / advisory
View advisory
CVSS Score v3.1 3.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N
EPSS Score 0.0048 39th percentile
Risk Priority 32 floored blend · peak EPSS

Summary

CVE-2023-3906 is a low-severity Improper Validation of Specified Type of Input (CWE-1287) vulnerability in Gitlab Gitlab. Its CVSS base score is 3.5 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 39th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

An input validation issue in the asset proxy in GitLab EE, affecting all versions from 12.3 prior to 16.2.8, 16.3 prior to 16.3.5, and 16.4 prior to 16.4.1, allowed an authenticated attacker to craft image urls which bypass the asset…

more

proxy.

CWE(s)
CWE-1287NVD-CWE-Other

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-3900Same product: Gitlab Gitlab
CVE-2023-3917Same product: Gitlab Gitlab
CVE-2023-4522Same product: Gitlab Gitlab
CVE-2023-3904Same product: Gitlab Gitlab
CVE-2026-2370Same product: Gitlab Gitlab
CVE-2026-0723Same product: Gitlab Gitlab
CVE-2026-1101Same product: Gitlab Gitlab
CVE-2025-13078Same product: Gitlab Gitlab
CVE-2025-14869Same product: Gitlab Gitlab
CVE-2025-2256Same product: Gitlab Gitlab

Affected Assets

gitlab
gitlab
16.4.0 · 12.3 — 16.2.8 · 12.3 — 16.2.8 · 16.3.0 — 16.3.5

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.1.1
  • V1.4.2
  • V2.1.1
  • V2.2.2

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.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require proper input type validation during development.

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.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect type-validation flaws but does not prevent them during development.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates input validation and type checking to prevent improper type handling.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly include validation of input data types and formats.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles promote defensive input handling and type enforcement at system boundaries.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly require proper type validation of all external inputs.

References