# CVE-2023-51380: Incorrect Authorization allows Read Access to Issue Comments in GitHub Enterprise Server

> Attackers with improperly scoped tokens can read issue comments due to incorrect authorization checks in GitHub Enterprise Server.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Dec 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-rqgv-j8f8-5q7x

## What is CVE-2023-51380?

CVE-2023-51380 is a low-severity missing authorization vulnerability in Github Enterprise Server, published on 21 Dec 2023. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An incorrect authorization vulnerability was identified in GitHub Enterprise Server that allowed issue comments to be read with an improperly scoped token. This vulnerability affected all versions of GitHub Enterprise Server since 3.7 and was fixed in version 3.7.19, 3.8.12, 3.9.7, 3.10.4, and 3.11.1.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2023-51380?

It affects 1 product.


Products: Github Enterprise Server.

## How do I fix CVE-2023-51380?

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

## Is CVE-2023-51380 being exploited?

There is no known exploitation of CVE-2023-51380 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-23739](https://insights.sbomify.com/CVE-2022-23739/): Missing authorization in GitHub Enterprise Server (critical 9.8)
- [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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-51380 and fix it if it is affected.

What it is: CVE-2023-51380 is a low-severity missing authorization vulnerability in Github Enterprise Server, published on 21 Dec 2023. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-51380 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-2023-51380/ (Markdown: https://insights.sbomify.com/CVE-2023-51380/index.md)
```

## Sources

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

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