Enterprise ServerApplication · GitHub
CVE-2022-23733
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 · uneditedA stored XSS vulnerability was identified in GitHub Enterprise Server that allowed the injection of arbitrary attributes. This injection was blocked by Github's Content Security Policy (CSP). This vulnerability affected all versions of GitHub Enterprise Server prior to 3.6 and was fixed in versions 3.3.11, 3.4.6 and 3.5.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 · high confidenceA stored XSS vulnerability in GitHub Enterprise Server allowed injection of arbitrary attributes into web content. While the injected payload was blocked from executing due to the Content Security Policy, the vulnerability still represented a security weakness in how user-supplied attributes were handled. The CSP mitigation kept the severity at medium (CVSS 5.4).
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
>= 3.3.0, < 3.3.11>= 3.4.0, < 3.4.6>= 3.5.0, < 3.5.3CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify GitHub Enterprise Server versionLog into the management console or admin dashboard. Navigate to the About or Settings section to view the exact version number. Alternatively, access the server via SSH and run: cat /usr/local/github/versionAffected if The installed version falls within these ranges: 3.3.0 to 3.3.10, 3.4.0 to 3.4.5, or 3.5.0 to 3.5.2
-
Confirm the web interface is accessibleVerify that the GitHub web interface is running and accessible to users. The vulnerability affects how user-supplied attributes are rendered in web content.Affected if The web interface is enabled and users can interact with content creation features where attributes could be injected
-
Check if user content features are activeReview whether the instance has user-facing features that accept user-supplied content such as issues, pull requests, discussions, or markdown rendering. These are the vectors where attribute injection could occur.Affected if Users have the ability to create or modify content that gets rendered with attributes in the web interface
You are affected if your GitHub Enterprise Server version is 3.3.x before 3.3.11, 3.4.x before 3.4.6, or 3.5.x before 3.5.3, and the web interface with user content features is enabled.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.3.113.4.63.5.3
Upgrade GitHub Enterprise Server to version 3.3.11, 3.4.6, 3.5.3 or later. The CSP provided partial protection but the underlying vulnerability requires the patched version for complete remediation.
3.3.11, 3.4.6, 3.5.3, or 3.6+ (whichever is compatible with your current branch)
- 1. Identify the current GitHub Enterprise Server version by accessing the Management Console or running: ghe-version
- 2. Determine which upgrade path applies based on current version: if >= 3.3.0 and < 3.3.11, upgrade to 3.3.11; if >= 3.4.0 and < 3.4.6, upgrade to 3.4.6; if >= 3.5.0 and < 3.5.3, upgrade to 3.5.3
- 3. Alternatively, upgrade to version 3.6.0 or later which contains the fix
- 4. Before upgrading, review GitHub Enterprise Server release notes for any known issues
- 5. Perform the upgrade following standard GitHub Enterprise Server upgrade procedures
- 6. After upgrade, verify the version has been updated correctly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Enterprise Server
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-23733 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-23733 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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