# CVE-2024-6336: Security misconfiguration was identified in GitHub Enterprise Server that allowed sensitive data exposure

> Unauthorized users could access sensitive data via organization rulesets if a member changed repository visibility, requiring an upgrade to GitHub Enterprise Server.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/S:N/AU:N/R:U/U:Amber`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Jul 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-gch4-6c9x-v2fr

## What is CVE-2024-6336?

CVE-2024-6336 is a medium-severity vulnerability in Github Enterprise Server, published on 16 Jul 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A Security Misconfiguration vulnerability in GitHub Enterprise Server allowed sensitive information disclosure to unauthorized users in GitHub Enterprise Server by exploiting organization ruleset feature. This attack required an organization member to explicitly change the visibility of a dependent repository from private to public. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.14 and was fixed in versions 3.13.1, 3.12.6, 3.11.12, 3.10.14, and 3.9.17. This vulnerability was reported via the GitHub Bug Bounty program.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2024-6336?

It affects 1 product.


Products: Github Enterprise Server.

## How do I fix CVE-2024-6336?

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

## Is CVE-2024-6336 being exploited?

There is no known exploitation of CVE-2024-6336 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-2024-6336 and fix it if it is affected.

What it is: CVE-2024-6336 is a medium-severity vulnerability in Github Enterprise Server, published on 16 Jul 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-6336 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-2024-6336/ (Markdown: https://insights.sbomify.com/CVE-2024-6336/index.md)
```

## Sources

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

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