Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_P

CVE-2023-51379: Incorrect Authorization for Issue Comments in GitHub Enterprise Server

Noroxi assessment

Priority: Monitor (action score 19/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.61% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: GitHub Enterprise Server 3.10.4, 3.11.1, 3.7.19.

Low priority for now. Upgrade to GitHub Enterprise Server 3.10.4, 3.11.1, 3.7.19 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

An incorrect authorization vulnerability was identified in GitHub Enterprise Server that allowed issue comments to be updated with an improperly scoped token. This vulnerability did not allow unauthorized access to any repository content as it also required contents:write and issues:read permissions. This vulnerability affected all versions of GitHub Enterprise Server since 3.7 and was fixed in version 3.17.19, 3.8.12, 3.9.7, 3.10.4, and 3.11.1. 

MediumCVSS 4.9 · v3.1—No exploit Fix available
Published
Dec 21, 2023
Updated
Jun 17, 2026
EPSS
0.6% · 49th percentile

Report tools

JSON

Action score

19

Monitor

Low priority for now.

CVSS
19 / 40 · 4.9 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.6%

CNA vs NVD score

NVD
4.9
CNA · GitHub_P
4.9
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2023-51379

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for github records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
githubenterprise server

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • github enterprise server3.7.0 and later · before 3.7.19
  • github enterprise server3.8.0 and later · before 3.8.12
  • github enterprise server3.9.0 and later · before 3.9.7
  • github enterprise server3.10.0 and later · before 3.10.4
  • github enterprise server3.11.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_P). Independent of NVD's CPE analysis and usually ahead of it.

  • GitHub Enterprise Server

    • 3.7.0 and later · up to and including 3.7.18affected · semverfixed in 3.7.19
    • 3.8.0 and later · up to and including 3.8.11affected · semverfixed in 3.8.12
    • 3.9.0 and later · up to and including 3.9.6affected · semverfixed in 3.9.7
    • 3.10.0 and later · up to and including 3.10.3affected · semverfixed in 3.10.4
    • 3.11 and later · up to and including 3.11.0affected · semverfixed in 3.11.1

Same product

github: all records

Other highest-scoring records for the same primary product.

  • CVE-2024-0200Unsafe Reflection in Github Enterprise Server leading to Command Injection
    61This week
  • CVE-2024-0507Privilege Escalation by Code Injection in the Management Console in GitHub Enterprise Server
    55Plan
  • CVE-2026-3854Remote code execution via git push option injection in GitHub Enterprise Server
    46Plan

Published before and after this one in the same product

  • ← EarlierCVE-2023-46648Dec 21, 2023 · Insufficient Entropy in GitHub Enterprise Server Management Console Invitation Token
    30Monitor
  • ← EarlierCVE-2023-46649Dec 21, 2023 · Race Condition allows Administrative Access on Organization Repositories
    28Monitor
  • Later →CVE-2023-51380Dec 21, 2023 · Incorrect Authorization allows Read Access to Issue Comments in GitHub Enterprise Server
    17Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
GitHub Enterprise Server3.10.4Vendor (CNA)
GitHub Enterprise Server3.11.1Vendor (CNA)
GitHub Enterprise Server3.7.19Vendor (CNA)
GitHub Enterprise Server3.8.12Vendor (CNA)
GitHub Enterprise Server3.9.7Vendor (CNA)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2022-23739338 days apartIncorrect authorization check in GitHub Enterprise Server leading to escalation of privileges in GraphQL API requests from GitHub Apps using scoped user-to-serv
    39Monitor
  • CVE-2022-23741372 days apartIncorrect authorization in GitHub Enterprise Server token generation leading to full admin access
    28Monitor
  • CVE-2024-5816208 days apartImproper authorization allows persistent access in GitHub Enterprise Server
    27Monitor
  • CVE-2024-148255 days apartImproper Authorization in GitHub Enterprise Server allowed unauthorized workflow execution
    26Monitor
  • CVE-2022-46258346 days apartIncorrect Authorization in GitHub Enterprise Server leads to Action Workflow modifications without Workflow Scope
    26Monitor
  • CVE-2024-5817208 days apartImproper authorization allows read access to issue content in GitHub Enterprise Server
    23Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • Administrator privileges are required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
high · data or configuration can be modified
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
High
Availability impact
None

Weakness class (CWE)

CWE-863 · Incorrect Authorization

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (4 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records