dbcve.org
Enterprise ServerApplication · GitHub

CVE-2022-23734

HIGH · 8.8 CVSS v3.1 Published 2022-10-19
Fix available
A fix is available. Upgrade to 3.2.16 / 3.3.11 or later.
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
A deserialization of untrusted data vulnerability was identified in GitHub Enterprise Server that could potentially lead to remote code execution on the SVNBridge. To exploit this vulnerability, an attacker would need to gain access via a server-side request forgery (SSRF) that would let an attacker control the data being deserialized. This vulnerability affected all versions of GitHub Enterprise Server prior to v3.6 and was fixed in versions 3.5.3, 3.4.6, 3.3.11, and 3.2.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

A deserialization vulnerability in GitHub Enterprise Server's SVNBridge component allows remote code execution through SSRF. Attackers can exploit SSRF to supply malicious serialized data that gets deserialized without proper validation, potentially executing arbitrary code on the affected system.

MitigationUpgrade GitHub Enterprise Server to version 3.6 or later (or at minimum to one of the fixed versions: 3.5.3, 3.4.6, 3.3.11, 3.2.16). If immediate patching is not feasible, disable the SVNBridge component if not required and implement network-level controls to restrict SSRF attack vectors.

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.2.16>= 3.3.0, < 3.3.11>= 3.4.0, < 3.4.6>= 3.5.0, < 3.5.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
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
    Run 'ghe-version' from the management shell or check the /setup/api/settings endpoint on the appliance
    Affected if The version is less than 3.2.16, between 3.3.0-3.3.11, between 3.4.0-3.4.6, or between 3.5.0-3.5.3
  2. Confirm SVNBridge is enabled
    Check theSVNBridge settings in the GitHub Enterprise Admin Center under 'Developer settings' or by querying the /setup/api/configure endpoint for the svn-landing-url configuration
    Affected if SVNBridge is enabled and accessible; the vulnerability only applies when the component is running
  3. Verify SSRF-exposed endpoints
    Review the SVNBridge network accessibility - check if port 8080 is open or if the '/svn/' endpoint is reachable from untrusted networks
    Affected if SVNBridge endpoint is reachable from the network where an attacker could send malicious requests
  4. Review deserialization sinks
    Examine the SVNBridge request handling code or logs for Java object deserialization patterns (look for serialized Java objects in request bodies)
    Affected if SVNBridge processes serialized data without validation - this is the core vulnerability condition but is inherent to the affected version regardless of config

You are affected if GitHub Enterprise Server runs an affected version (see version ranges) AND SVNBridge is enabled and accessible

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.2.16 / 3.3.11 / 3.4.6 or later
Fixed in 3.2.163.3.113.4.6
Interim mitigation

Upgrade GitHub Enterprise Server to version 3.6 or later (or at minimum to one of the fixed versions: 3.5.3, 3.4.6, 3.3.11, 3.2.16). If immediate patching is not feasible, disable the SVNBridge component if not required and implement network-level controls to restrict SSRF attack vectors.

Recommended fix High confidence

Upgrade to version 3.2.16, 3.3.11, 3.4.6, or 3.5.3 (or later, preferably latest stable)

  1. 1. Identify the current GitHub Enterprise Server version by navigating to the Management Console or running: ghe-version
  2. 2. Take a complete backup of the GitHub Enterprise Server instance, including database, Git repositories, and configuration
  3. 3. Review the upgrade path documentation at docs.github.com to ensure compatibility with your current version
  4. 4. Upgrade to one of the fixed versions: 3.2.16, 3.3.11, 3.4.6, or 3.5.3 (or later, ideally the latest stable release)
  5. 5. Follow the standard GitHub Enterprise Server upgrade procedure using the hotupgrade or backup-restore method as appropriate
  6. 6. Verify the upgrade was successful by checking the version and ensuring core services are operational

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 / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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