GitLab: Improper Neutralization of Special Elements used in a Command
CVE-2024-8640 is a high-severity improper neutralization of special elements used in a command vulnerability in GitLab, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists versions 17.1.7, 17.2.5, 17.3.2 as the first without the flaw, so updating GitLab to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.99% chance of exploitation within 30 days, higher than 63% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update GitLab to 17.1.7 or 17.2.5 or 17.3.2, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| GitLab | GitLab | 16.11 up to, but not including, 17.1.7; 17.2 up to, but not including, 17.2.5; 17.3 up to, but not including, 17.3.2 | 17.1.7, 17.2.5, 17.3.2 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 8.5 | High | CNA (gitlab.com) |
| CVSS 3.1 | 8.8 | High | NVD |
Official description
An issue has been discovered in GitLab EE affecting all versions starting from 16.11 prior to 17.1.7, from 17.2 prior to 17.2.5, and from 17.3 prior to 17.3.2. Due to incomplete input filtering, it was possible to inject commands into a connected Cube server.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Neutralization of Special Elements used in a Command
The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.
How developers prevent this class of flaw
- If at all possible, use library calls rather than external processes to recreate the desired functionality.
- If possible, ensure that all external commands called from the program are statically created.
- Run time: Run time policy enforcement may be used in an allowlist fashion to prevent use of any non-sanctioned commands.
More Improper Neutralization of Special Elements used in a Command vulnerabilities (CWE-77)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Other references
- hackerone.com/reports/2687770Permissions Required
Other vulnerabilities in GitLab
- 7.1 High severity
- 8.2 High severity
- 7.5 High severity
- 10.0 Critical severity
- 10.0 Critical severity
- 7.3 High severity
Recent Improper Neutralization of Special Elements used in a Command vulnerabilities
- 9.8 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
- 7.3 High severity
- 7.6 High severity
- 8.8 High severity
Spotted an error? Tell us.