GitHub Enterprise Server: Improper Limitation of a Pathname to a Restricted Directory
CVE-2022-23732 is a high-severity improper limitation of a pathname to a restricted directory vulnerability in GitHub Enterprise Server from GitHub, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. The record lists versions 3.1.19, 3.2.11, 3.3.6 as the first without the flaw, so updating GitHub Enterprise Server to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 1.74% chance of exploitation within 30 days, higher than 78% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update GitHub Enterprise Server to 3.1.19 or 3.2.11 or 3.3.6 or 3.4.1, whichever matches your release line, or a later version.
- Update Enterprise Server to 3.1.19 or 3.2.11 or 3.3.6 or 3.4.1, whichever matches your release line, or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
- Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| GitHub | GitHub Enterprise Server | 3.1 up to, but not including, 3.1.19; 3.2 up to, but not including, 3.2.11; 3.3 up to, but not including, 3.3.6; 3.4 up to, but not including, 3.4.1 | 3.1.19, 3.2.11, 3.3.6, 3.4.1 |
| GitHub | Enterprise Server | before 3.1.19; 3.2.0 up to, but not including, 3.2.11; 3.3.0 up to, but not including, 3.3.6; 3.4.0 up to, but not including, 3.4.1 | 3.1.19, 3.2.11, 3.3.6, 3.4.1 |
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
- RequiredA user must take an action such as opening a file or link.
- 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:N/UI:R/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 8.8 | High | NVD |
| CVSS 2.0 | 6.8 | Medium | NVD |
Official description
A path traversal vulnerability was identified in GitHub Enterprise Server management console that allowed the bypass of CSRF protections. This could potentially lead to privilege escalation. To exploit this vulnerability, an attacker would need to target a user that was actively logged into the management console. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.5 and was fixed in versions 3.1.19, 3.2.11, 3.3.6, 3.4.1. This vulnerability was reported via the GitHub Bug Bounty program.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Limitation of a Pathname to a Restricted Directory
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
How developers prevent this class of flaw
- For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
- Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth.
More Improper Limitation of a Pathname to a Restricted Directory vulnerabilities (CWE-22)
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Other vulnerabilities in GitHub Enterprise Server
- 7.6 High severity
- 9.8 Critical severity
- 7.2 High severity
- 7.2 High severity
- 9.8 Critical severity
- 7.2 High severity
Recent Improper Limitation of a Pathname to a Restricted Directory vulnerabilities
- 7.5 High severity
- 7.5 High severity
- 8.8 High severity
- 7.5 High severity
- 7.5 High severity
- 9.8 Critical severity
Spotted an error? Tell us.