dbcve.org
Enterprise ServerApplication · GitHub

CVE-2024-10824

MEDIUM · 6.5 CVSS v3.1 Published 2024-11-07
Fix available
A fix is available. Upgrade to 3.13.2 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 authorization bypass vulnerability was identified in GitHub Enterprise Server that allowed unauthorized internal users to access sensitive secret scanning alert data intended only for business owners. This issue could be exploited only by organization members with a personal access token (PAT) and required that secret scanning be enabled on user-owned repositories. This vulnerability affected GitHub Enterprise Server versions after 3.13.0 but prior to 3.14.0 and was fixed in version 3.13.2.

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 authorization bypass vulnerability in GitHub Enterprise Server allowed organization members with personal access tokens (PATs) to access secret scanning alert data that should only be visible to business owners. This occurred specifically when secret scanning was enabled on user-owned repositories, enabling unauthorized access to sensitive security alert information.

MitigationUpgrade GitHub Enterprise Server to version 3.13.2 or later. As a compensating control, review and restrict PAT access permissions and consider temporarily disabling secret scanning on user-owned repositories until the upgrade can be applied.

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.13.0, < 3.13.2

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. Determine your GitHub Enterprise Server version
    Log into the Management Console or administrative web interface and navigate to the settings or about page to find the installed version number
    Affected if The installed version is 3.13.0 or 3.13.1 (versions 3.13.0 through 3.13.1 are affected)
  2. Verify secret scanning is enabled
    Navigate to your organization or enterprise settings, then locate the Security section to check if Secret scanning is turned on for repositories
    Affected if Secret scanning is enabled globally or on user-owned repositories
  3. Identify user-owned repositories with secret scanning active
    Review repository settings across all organizations to identify any user-owned (personal) repositories where secret scanning alerts are being generated
    Affected if There are user-owned repositories with secret scanning enabled and alerts being generated

You are affected if your GitHub Enterprise Server runs version 3.13.0 or 3.13.1 AND secret scanning is enabled on user-owned repositories, allowing organization members with PATs to potentially view secret scanning alerts they should not access.

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.13.2 or later
Fixed in 3.13.2
Interim mitigation

Upgrade GitHub Enterprise Server to version 3.13.2 or later. As a compensating control, review and restrict PAT access permissions and consider temporarily disabling secret scanning on user-owned repositories until the upgrade can be applied.

Recommended fix High confidence

GitHub Enterprise Server 3.13.2 or later (recommended: latest stable 3.x release)

  1. Back up your GitHub Enterprise Server instance data and configuration before proceeding with the upgrade
  2. Upgrade GitHub Enterprise Server to version 3.13.2 or later (3.14.0 and beyond include the fix)
  3. After upgrade, verify that secret scanning is properly configured on user-owned repositories
  4. Review organization access controls and personal access tokens (PATs) to ensure they follow least-privilege principles
  5. Confirm the authorization fix is working by testing that only business owners can access secret scanning alert data
Caveat Review GitHub Enterprise Server release notes for 3.13.2 and subsequent releases for any breaking changes that may affect your instance

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

Fix this in Enterprise Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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