dbcve.org
Enterprise ServerApplication · GitHub

CVE-2022-46255

CRITICAL · 9.8 CVSS v3.1 Published 2022-12-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
An improper limitation of a pathname to a restricted directory vulnerability was identified in GitHub Enterprise Server that enabled remote code execution. A check was added within Pages to ensure the working directory is clean before unpacking new content to prevent an arbitrary file overwrite bug. 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

A path traversal vulnerability in GitHub Enterprise Server's Pages feature allowed remote code execution by not validating that the working directory was clean before unpacking new content. This improper limitation of pathname to a restricted directory enabled arbitrary file overwrite, specifically affecting only version 3.7.0.

MitigationUpgrade GitHub Enterprise Server from version 3.7.0 to version 3.7.1 or later to apply the fix that adds the working directory validation check before unpacking content.

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

CVSS:3.1/AV:N/AC:L/PR:N/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 installed GitHub Enterprise Server version
    Access the GitHub Enterprise Server admin console or run the administrative command to retrieve the current version (typically via the Management Console or ghe-version command in the admin shell).
    Affected if The reported version is exactly 3.7.0 (no other versions are affected).
  2. Confirm Pages feature is enabled
    Navigate to the GitHub Enterprise Server admin settings and verify the status of the Pages feature under Site Admin > Pages settings, or check the configuration files that control the Pages service.
    Affected if The Pages feature is currently enabled or has been enabled at any point while running version 3.7.0.
  3. Verify Pages sites exist or were created
    Check if any Pages sites have been published on the GitHub Enterprise Server instance by reviewing the Pages configuration, site storage, or repository settings that expose Pages functionality.
    Affected if At least one Pages site exists or was created while running version 3.7.0, as this provides the attack surface for the path traversal during content unpacking.

You are affected if your GitHub Enterprise Server is exactly version 3.7.0 and the Pages feature has been enabled or used to host any content.

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 fix that adds the working directory validation check before unpacking content.

Recommended fix High confidence

3.7.1

  1. Back up your GitHub Enterprise Server instance before upgrading
  2. Review the release notes for version 3.7.1 to understand changes and verify compatibility
  3. Upgrade your GitHub Enterprise Server instance from version 3.7.0 to version 3.7.1
  4. After upgrade, verify that GitHub Pages functionality is working correctly
  5. Confirm the vulnerability is resolved by ensuring the path traversal check is in place
Caveat Check 3.7.1 release notes for any breaking changes or required migration steps before upgrading

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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