GitLab: Improper Encoding or Escaping of Output
CVE-2022-0741 is a high-severity improper encoding or escaping of output vulnerability in GitLab, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected GitLab versions: >=10.0, <14.6.5; >=14.7, <14.7.4; >=14.8, <14.8.2. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 1.48% chance of exploitation within 30 days, higher than 74% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of GitLab you run against the affected versions below, and install the vendor's latest release.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| GitLab | GitLab | >=10.0, <14.6.5; >=14.7, <14.7.4; >=14.8, <14.8.2 | Not stated |
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
- NoneNo account or login is needed.
- 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
- NoneNothing can be modified.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 5.8 | Medium | CNA (gitlab.com) |
| CVSS 3.1 | 7.5 | High | NVD |
| CVSS 2.0 | 4.3 | Medium | NVD |
Official description
Improper input validation in all versions of GitLab CE/EE using sendmail to send emails allowed an attacker to steal environment variables via specially crafted email addresses.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Encoding or Escaping of Output
The product prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. As a result, the intended structure of the message is not preserved.
How developers prevent this class of flaw
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using the ESAPI Encoding control or a similar tool, library, or framework. These will help the programmer encode outputs in a manner less prone to error. Alternately, use built-in functions, but consider using wrappers in case those functions are discovered to have a vulnerability.
- If available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated. For example, stored procedures can enforce database query structure and reduce the likelihood of SQL injection.
- Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages. Study all expected communication protocols and data representations to determine the required encoding strategies.
More Improper Encoding or Escaping of Output vulnerabilities (CWE-116)
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-0741.jsonThird Party Advisory
- gitlab.com/gitlab-org/gitlab/-/issues/337601Issue Tracking, Third Party Advisory
- hackerone.com/reports/1286317Permissions Required, Third Party Advisory
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 Encoding or Escaping of Output vulnerabilities
- 9.8 Critical severity
- 8.1 High severity
- 9.8 Critical severity
- 6.1 Medium severity
- 9.8 Critical severity
Spotted an error? Tell us.