dbcve.org
Enterprise ServerApplication · GitHub

CVE-2024-6336

MEDIUM · 5.3 CVSS v3.1 Published 2024-07-16
Fix available
A fix is available. Upgrade to 3.9.17 / 3.10.14 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A Security Misconfiguration in GitHub Enterprise Server allowed unauthorized users to access sensitive information through the organization ruleset feature. The attack required an organization member to explicitly change a dependent repository's visibility from private to public, exposing data that should have remained protected.

MitigationUpgrade GitHub Enterprise Server to version 3.13.1, 3.12.6, 3.11.12, 3.10.14, 3.9.17 or later. Additionally, audit organization rulesets to restrict or monitor repository visibility changes to prevent inadvertent sensitive data exposure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Enterprise ServerApplication
Affected:>= 3.9.0, < 3.9.17>= 3.10.0, < 3.10.14>= 3.11.0, < 3.11.12>= 3.12.0, < 3.12.6= 3.13.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify GitHub Enterprise Server version
    Access the GitHub Enterprise Server admin dashboard, go to the Management Console or check /api/v3/enterprise for the installed_version. Alternatively, run 'ghe-version' from the administrative shell if available.
    Affected if The installed version falls within any of these ranges: 3.9.0-3.9.16, 3.10.0-3.10.13, 3.11.0-3.11.11, 3.12.0-3.12.5, or exactly 3.13.0.
  2. Review organization rulesets for visibility rules
    Navigate to each organization's Settings > Rules > Rulesets (or /organizations/ORG/settings/rulesets). Inspect rulesets that include 'Change repository visibility' as a permitted action.
    Affected if An organization has active rulesets that allow repository visibility changes without sufficient restrictions or without blocking the change.
  3. Audit recent repository visibility changes
    Use the GitHub API or audit log (Organization settings > Audit log) to query for events involving repository visibility changes. Look for events where 'visibility' changed from 'private' to 'public'.
    Affected if Any dependent or internal repository within an organization has had its visibility changed from private to public after the ruleset was configured.
  4. Check ruleset enforcement status
    In each organization's rulesets, verify whether rules controlling visibility changes are set to 'Evaluate' (non-blocking) or actively 'Enforce'.
    Affected if Rulesets that govern repository visibility changes are set to passive evaluation rather than active enforcement.

You are affected if your GHES version is within the vulnerable ranges listed AND your organization has rulesets that permit repository visibility changes from private to public without strict enforcement.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.9.17 / 3.10.14 / 3.11.12 or later
Fixed in 3.9.173.10.143.11.12
Interim mitigation

Upgrade GitHub Enterprise Server to version 3.13.1, 3.12.6, 3.11.12, 3.10.14, 3.9.17 or later. Additionally, audit organization rulesets to restrict or monitor repository visibility changes to prevent inadvertent sensitive data exposure.

Recommended fix High confidence

Upgrade to the patched version within your current release branch: 3.9.17 (for 3.9.x), 3.10.14 (for 3.10.x), 3.11.12 (for 3.11.x), 3.12.6 (for 3.12.x), or 3.13.1 (for 3.13.x)

  1. Backup all GitHub Enterprise Server data and configurations before proceeding with the upgrade
  2. Review the GitHub Enterprise Server upgrade documentation for your current version to ensure compatibility
  3. Schedule a maintenance window as upgrades require downtime
  4. Download the appropriate patched release for your current version branch (3.9.17, 3.10.14, 3.11.12, 3.12.6, or 3.13.1)
  5. Follow the standard GitHub Enterprise Server upgrade procedure using the admin console or command-line interface
  6. After upgrade completes, verify the version number matches the expected patched version
  7. Test that organization ruleset functionality works correctly post-upgrade
  8. Confirm the vulnerability is remediated by verifying that changing a dependent repository visibility no longer exposes sensitive information to unauthorized users
Caveat Standard GitHub Enterprise Server upgrade considerations apply; review release notes for your target version for any potential breaking changes or required migration steps

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Enterprise Server Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,260
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,816.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-6336 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-6336 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data