CVE-2024-5528
Gitlab ≤ 16.11.6
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:NSummary
CVE-2024-5528 is a low-severity Incomplete Comparison with Missing Factors (CWE-1023) vulnerability in Gitlab Gitlab. Its CVSS base score is 3.5 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique Obfuscated Files or Information (T1027); ranked at the 33th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and AC-24 (Access Control Decisions) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-47165
Vulnerability Data
An issue was discovered in GitLab CE/EE affecting all versions prior to 16.11.6, starting from 17.0 prior to 17.0.4, and starting from 17.1 prior to 17.1.2, which allows a subdomain takeover in GitLab Pages.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V6.3.4V6.3.5V6.1.3V6.5.7
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation directly exercises security-relevant comparisons to discover incorrect logic.
Mandating that access-control decisions apply the full set of required rules to each request structurally eliminates missing-factor comparisons.
A reference monitor must be small and correct, structurally limiting the chance of flawed comparison logic in authorization decisions.
Access enforcement requires that every authorization decision evaluate all relevant entity attributes, directly stopping incomplete comparisons from being used.
Security engineering principles require correct implementation of comparison logic used for access and authentication decisions.
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 (reviews, testing, static analysis) directly prevent incomplete comparison flaws from being introduced.
Authentication decisions often rely on multi-factor comparisons; incomplete comparisons directly weaken this control.
Enforcing access policy requires complete evaluation of all relevant attributes; missing factors undermine authorization decisions.
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 can detect missing comparison factors, yet testing is only one part of the control's scope.
Secure development lifecycle includes code review and testing that can catch incorrect comparison logic.
Application security requirements can mandate complete multi-factor comparisons, but the control is broader than this single weakness.
Secure architecture principles can require exhaustive entity comparisons, yet the control addresses many other design concerns.
Secure coding standards can forbid incomplete comparisons, but the control covers a wide range of coding issues.
Secure authentication mechanisms rely on correct comparison of credentials or tokens.