dbcve.org
Enterprise ServerApplication · GitHub

CVE-2022-23737

MEDIUM · 6.5 CVSS v3.1 Developing Published 2022-12-01
Fix available
A fix is available. Upgrade to 3.2.20 / 3.3.15 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 improper privilege management vulnerability was identified in GitHub Enterprise Server that allowed users with improper privileges to create or delete pages via the API. To exploit this vulnerability, an attacker would need to be added to an organization's repo with write permissions. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.7 and was fixed in versions 3.2.20, 3.3.15, 3.4.10, 3.5.7, and 3.6.3. 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 · low confidence
Developing — this CVE was published recently and its authoritative NVD entry is still being established, so we're holding a technical summary until the source data settles rather than publish something unreliable. Re-checking after 2026-08-01.

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.2.20>= 3.3.0, < 3.3.15>= 3.4.0, < 3.4.10>= 3.5.0, < 3.5.7>= 3.6.0, < 3.6.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
None
Integrity
High
Availability
None

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

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.2.20 / 3.3.15 / 3.4.10 or later
Fixed in 3.2.203.3.153.4.10
Recommended fix High confidence

3.2.20, 3.3.15, 3.4.10, 3.5.7, or 3.6.3 (whichever is the next stable release for your current branch)

  1. 1. Identify the current GitHub Enterprise Server version by navigating to the Management Console or using the administrative API
  2. 2. Determine the appropriate upgrade path based on current version: if < 3.2.20 upgrade to 3.2.20; if >= 3.3.0 and < 3.3.15 upgrade to 3.3.15; if >= 3.4.0 and < 3.4.10 upgrade to 3.4.10; if >= 3.5.0 and < 3.5.7 upgrade to 3.5.7 or 3.6.3
  3. 3. Review GitHub Enterprise Server upgrade documentation for the target version
  4. 4. Create a complete backup of the GitHub Enterprise Server instance including database and filesystem
  5. 5. Schedule maintenance window as upgrades require downtime
  6. 6. Download the upgrade package from GitHub Enterprise downloads
  7. 7. Follow standard GitHub Enterprise Server upgrade procedure to apply the update
  8. 8. Verify the upgrade was successful by checking the version in the Management Console
Caveat Standard upgrade risks apply - review release notes for any configuration or migration requirements

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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