Security readout for executives and security teams
Plain-English summary
GitLab EE had a permissions flaw where Guest users could change Custom dashboard projects settings they should not control. The impact is limited to integrity of that setting, not data disclosure or service outage. Organizations running affected GitLab EE versions should upgrade to the fixed releases or later.
Executive priority
Treat this as a routine but necessary GitLab maintenance update. It does not indicate data theft or outage risk from the provided evidence, but it allows unauthorized configuration changes by low-privileged users and should be closed in the next normal patch cycle.
Technical view
CVE-2024-0861 is a CWE-425 forced-browsing issue in GitLab EE. A low-privileged authenticated Guest could directly access functionality to change Custom dashboard projects settings contrary to intended permissions. Affected ranges are 16.4 before 16.7.6, 16.8 before 16.8.3, and 16.9 before 16.9.1.
Likely exposure
Exposure is limited to GitLab EE deployments in the affected version ranges with users holding Guest access. GitLab installations outside those ranges, or not using EE, are not identified as affected in the provided sources.
Exploitation context
The CVE is not listed as KEV in the source bundle, and no cited source states active exploitation. The HackerOne reference is tagged as an exploit/technical report, but the provided bundle does not include operational details and should not be treated as evidence of broad exploitation.
Researcher notes
The public record identifies forced browsing and improper authorization around Custom dashboard projects settings. CVSS is 4.3 with low privileges, network access, no user interaction, and integrity-only impact. The source bundle does not provide enough detail to validate exploit mechanics safely or infer additional affected components.
Mitigation direction
- Upgrade GitLab EE to 16.7.6, 16.8.3, 16.9.1, or later.
- Review GitLab vendor guidance for any version-specific remediation notes.
- Audit Guest membership on projects and groups using custom dashboards.
- Restrict Guest access where it is not business-required.
- Review recent changes to Custom dashboard projects settings.
Validation and detection
- Inventory GitLab EE versions across self-managed deployments.
- Confirm no instance runs 16.4-16.7.5, 16.8-16.8.2, or 16.9.0.
- Check whether Custom dashboard projects settings are used.
- Review audit logs for unexpected dashboard setting changes by Guest users.
- Perform permission regression testing in a controlled non-production environment.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-425: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2024-0861 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- GitLab Issue #439240CVE reference · issue-tracking, permissions-required
- HackerOne Bug Bounty Report #2316435CVE reference · technical-description, exploit
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Direct Request ('Forced Browsing')
Direct Request ('Forced Browsing') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.