GitHub Enterprise Server: Incorrect Authorization
CVE-2022-23739 is a critical-severity incorrect authorization vulnerability in GitHub Enterprise Server from GitHub, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 3.3.16, 3.4.11, 3.5.8 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.28% chance of exploitation within 30 days, higher than 70% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update GitHub Enterprise Server to 3.3.16 or 3.4.11 or 3.5.8 or 3.6.4, whichever matches your release line, or a later version.
- Update Enterprise Server to 3.3.16 or 3.4.11 or 3.5.8 or 3.6.4, 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.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| GitHub | GitHub Enterprise Server | 3.3 up to, but not including, 3.3.16; 3.4 up to, but not including, 3.4.11; 3.5 up to, but not including, 3.5.8; 3.6 up to, but not including, 3.6.4; 3.7 up to, but not including, 3.7.1 | 3.3.16, 3.4.11, 3.5.8, 3.6.4, 3.7.1 |
| GitHub | Enterprise Server | before 3.3.16; 3.4.0 up to, but not including, 3.4.11; 3.5.0 up to, but not including, 3.5.8; 3.6.0 up to, but not including, 3.6.4; 3.7.0 | 3.3.16, 3.4.11, 3.5.8, 3.6.4 |
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
- 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:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 9.8 | Critical | NVD |
| CVSS 3.1 | 9.8 | Critical | CISA (ADP) |
Official description
An incorrect authorization vulnerability was identified in GitHub Enterprise Server, allowing for escalation of privileges in GraphQL API requests from GitHub Apps. This vulnerability allowed an app installed on an organization to gain access to and modify most organization-level resources that are not tied to a repository regardless of granted permissions, such as users and organization-wide projects. Resources associated with repositories were not impacted, such as repository file content, repository-specific projects, issues, or pull requests. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.7.1 and was fixed in versions 3.3.16, 3.4.11, 3.5.8, 3.6.4, 3.7.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: Incorrect Authorization
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
How developers prevent this class of flaw
- Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
- Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor.
- 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 authorization frameworks such as the JAAS Authorization Framework and the OWASP ESAPI Access Control feature.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- docs.github.com/en/enterprise-server%403.3/admin/release-notes#3.3.16
- docs.github.com/en/enterprise-server%403.4/admin/release-notes#3.4.11
- docs.github.com/en/enterprise-server%403.5/admin/release-notes#3.5.8
- docs.github.com/en/enterprise-server%403.6/admin/release-notes#3.6.4
- docs.github.com/en/enterprise-server%403.7/admin/release-notes#3.7.1
Other vulnerabilities in GitHub Enterprise Server
- 7.6 High severity
- 9.8 Critical severity
- 7.2 High severity
- 7.2 High severity
- 7.2 High severity
- 8.8 High severity
Recent Incorrect Authorization vulnerabilities
- 9.8 Critical severity
- 7.1 High severity
- 7.5 High severity
- 8.8 High severity
- 7.5 High severity
- 9.1 Critical severity
Spotted an error? Tell us.