dbcve.org
Enterprise ServerApplication · GitHub

CVE-2022-23740

HIGH · 8.8 CVSS v3.1 Published 2022-11-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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
CRITICAL: An improper neutralization of argument delimiters in a command vulnerability was identified in GitHub Enterprise Server that enabled remote code execution. To exploit this vulnerability, an attacker would need permission to create and build GitHub Pages using GitHub Actions. This vulnerability affected only version 3.7.0 of GitHub Enterprise Server and was fixed in version 3.7.1. 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

Command injection vulnerability in GitHub Enterprise Server 3.7.0 where improper neutralization of argument delimiters allows remote code execution via GitHub Actions when building GitHub Pages. Attack requires authenticated user with permission to create and build GitHub Pages.

MitigationUpgrade GitHub Enterprise Server from version 3.7.0 to version 3.7.1 or later to apply the vendor patch.

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

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

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
    Check the installed GitHub Enterprise Server version via the Management Console or by running 'ghe-version' command if you have SSH access to the appliance
    Affected if The installed version is exactly 3.7.0 (no other version is affected)
  2. Confirm GitHub Pages is accessible
    Verify whether the GitHub Pages feature is enabled in the organization or repository settings where Pages can be built
    Affected if GitHub Pages is enabled and users can trigger page builds (this is required for the attack surface to exist)
  3. Review user permissions for Pages creation
    Check which authenticated users have permissions to create and build GitHub Pages repositories in the environment
    Affected if Users with Pages build permissions exist in the environment (the vulnerability requires an authenticated user with this specific permission)
  4. Audit recent GitHub Actions workflows
    Review Actions workflow logs for any suspicious commands or unexpected behavior in Pages-related workflow runs around the time the vulnerability was disclosed
    Affected if Unusual or malicious commands appear in workflow execution logs for Pages builds

You are affected if running GitHub Enterprise Server exactly version 3.7.0 with GitHub Pages functionality enabled and users having permission to build Pages.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade GitHub Enterprise Server from version 3.7.0 to version 3.7.1 or later to apply the vendor patch.

Recommended fix High confidence

3.7.1

  1. Ensure you have a complete backup of your GitHub Enterprise Server instance
  2. Review the upgrade prerequisites for version 3.7.1 in the GitHub Enterprise Server documentation
  3. Perform the upgrade from version 3.7.0 to version 3.7.1 following the standard upgrade procedure
  4. Verify the upgrade was successful and the instance is operational
  5. Confirm the GitHub Pages and GitHub Actions features are functioning correctly

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

Fix this in Enterprise Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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