dbcve.org
Enterprise ServerApplication · GitHub

CVE-2024-6337

MEDIUM · 6.5 CVSS v3.1 Published 2024-08-20
Fix available
A fix is available. Upgrade to 3.10.16 / 3.11.14 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
An Incorrect Authorization vulnerability was identified in GitHub Enterprise Server that allowed a GitHub App with only content: read and pull_request_write: write permissions to read issue content inside a private repository. This was only exploitable via user access token and installation access token was not impacted. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.14 and was fixed in versions 3.13.3, 3.12.8, 3.11.14 and 3.10.16. 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

An incorrect authorization vulnerability in GitHub Enterprise Server allowed a GitHub App with only content:read and pull_request_write:write permissions to read issue content inside private repositories. This authorization bypass only occurred when using user access tokens; installation access tokens were not affected.

MitigationUpgrade GitHub Enterprise Server to version 3.13.3, 3.12.8, 3.11.14, or 3.10.16 or later to patch the authorization flaw. No configuration changes are required; the fix is in the server-side code.

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.10.0, < 3.10.16>= 3.11.0, < 3.11.14>= 3.12.0, < 3.12.8>= 3.13.0, < 3.13.3

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 Management Console and navigate to the 'About' page, or run 'ghe-version' from the administrative shell. The version is also visible in the footer of any admin page.
    Affected if The installed version falls within 3.10.0 to 3.10.15, 3.11.0 to 3.11.13, 3.12.0 to 3.12.7, or 3.13.0 to 3.13.2.
  2. Confirm use of GitHub Apps with restricted permissions
    Review all GitHub Apps installed in your enterprise. For each app, examine the permissions granted in the app settings. Specifically look for apps that have 'Content: Read' and 'Pull Requests: Write' permissions enabled.
    Affected if You have GitHub Apps with exactly or includes content:read and pull_request_write:write permissions.
  3. Determine token type in use
    Examine how external integrations or automated workflows authenticate. Check if they use user access tokens (generated via OAuth or personal access tokens) rather than installation access tokens (generated automatically for GitHub App installations). Review API call patterns or integration documentation.
    Affected if The affected GitHub Apps are being accessed using user access tokens rather than installation access tokens.
  4. Verify private repository issue access
    Test or audit whether the GitHub App with content:read and pull_request_write:write permissions can successfully read issue content from private repositories using a user access token via the REST API (GET /repos/{owner}/{repo}/issues/{issue_number}).
    Affected if The app can read issue content in private repositories when using a user access token despite lacking explicit issues:read permission.

You are affected if your GitHub Enterprise Server version is in the vulnerable range AND you use GitHub Apps with content:read plus pull_request_write:write permissions accessed via user access tokens, allowing unauthorized issue reading in private repos.

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.10.16 / 3.11.14 / 3.12.8 or later
Fixed in 3.10.163.11.143.12.8
Interim mitigation

Upgrade GitHub Enterprise Server to version 3.13.3, 3.12.8, 3.11.14, or 3.10.16 or later to patch the authorization flaw. No configuration changes are required; the fix is in the server-side code.

Recommended fix High confidence

3.13.3 (if on 3.13.x), 3.12.8 (if on 3.12.x), 3.11.14 (if on 3.11.x), or 3.10.16 (if on 3.10.x)

  1. 1. Identify your current GitHub Enterprise Server version by navigating to the Management Console or using the admin shell.
  2. 2. Determine which version line you are currently on (3.10.x, 3.11.x, 3.12.x, or 3.13.x).
  3. 3. For version 3.10.x: Upgrade to version 3.10.16 or later.
  4. 4. For version 3.11.x: Upgrade to version 3.11.14 or later.
  5. 5. For version 3.12.x: Upgrade to version 3.12.8 or later.
  6. 6. For version 3.13.x: Upgrade to version 3.13.3 or later.
  7. 7. After upgrading, verify the version change was successful and test that GitHub App permissions behave correctly (content:read with pull_request_write:write should no longer allow reading issue content in private repositories).
Caveat Standard GitHub Enterprise Server upgrade considerations apply - review release notes for your target version for any known issues or migration requirements

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

Fix this in Enterprise Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,590
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-6337 — 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-6337 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