# CVE-2022-23739: Missing authorization in GitHub Enterprise Server

> GitHub Apps with scoped tokens can bypass authorization to access and modify organization-level resources in GitHub Enterprise Server.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jan 2023
- **Updated:** 8 Apr 2025
- **Also known as:** GHSA-5863-jg7w-jf64

## What is CVE-2022-23739?

CVE-2022-23739 is a critical missing authorization vulnerability in Github Enterprise Server, published on 17 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### 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.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2022-23739?

It affects 1 product.


Products: Github Enterprise Server.

## How do I fix CVE-2022-23739?

No fix has been published for CVE-2022-23739 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-23739 being exploited?

There is no known exploitation of CVE-2022-23739 in the wild and no public exploit code.

## Other vulnerabilities in Github Enterprise Server

- [CVE-2024-4985](https://insights.sbomify.com/CVE-2024-4985/): Auth bypass in Enterprise Server (critical 10.0)
- [CVE-2022-46255](https://insights.sbomify.com/CVE-2022-46255/): Improper Limitation of a Pathname to a Restricted Directory in GitHub Enterprise Server leading to RCE (critical 9.8)
- [CVE-2021-22869](https://insights.sbomify.com/CVE-2021-22869/): Improper access control in GitHub Enterprise Server allows self-hosted runners to execute outside their control group (critical 9.8)
- [CVE-2024-9487](https://insights.sbomify.com/CVE-2024-9487/): Auth bypass in Enterprise Server (critical 9.5)
- [CVE-2024-6800](https://insights.sbomify.com/CVE-2024-6800/): Auth bypass in GitHub Enterprise Server (critical 9.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-23739 and fix it if it is affected.

What it is: CVE-2022-23739 is a critical missing authorization vulnerability in Github Enterprise Server, published on 17 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-23739 in the wild and no public exploit code.

Affected product: Github Enterprise Server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-23739/ (Markdown: https://insights.sbomify.com/CVE-2022-23739/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-23739
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-23739
- OSV: https://osv.dev/vulnerability/CVE-2022-23739

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-23739/
Summaries are generated and may contain mistakes; the official description above is the record.