CVE-2023-51380Network attack vector

Issue-comment disclosure via improper token-scope authorization

Published Dec 21, 2023 · Updated Aug 2, 2024

Incorrect authorization in GitHub Enterprise Server allows remote authenticated users to read issue comments with an improperly scoped token. The issue-comment authorization path accepts a token whose granted scope does not authorize access to the requested comments; GitHub has not disclosed the specific endpoint or code-level check. A valid high-privilege token and network access to the instance are required, and the documented consequence is limited to comment confidentiality.

CVSS severity4.3
Medium
EPSS probability0.47%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Incorrect authorization in GitHub Enterprise Server allows remote authenticated users to read issue comments with an improperly scoped token. The issue-comment authorization path accepts a token whose granted scope does not authorize access to the requested comments; GitHub has not disclosed the specific endpoint or code-level check. A valid high-privilege token and network access to the instance are required, and the documented consequence is limited to comment confidentiality.

The record

CVE
CVE-2023-51380
Published
Dec 21, 2023
Updated
Aug 2, 2024
Vendor
Twitter
Product
GitHub Enterprise Server
Classifications
CWE-863, CAPEC-114, T1213.003
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Dec 21, 2023CVE publishedPublication date reported by the CVE source.
  2. Aug 2, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=3.10.0 <=3.10.3 changes=[{"at":"3.10.4","status":"unaffected"}]
  2. Affected versionversion=3.11 <=3.11.0 changes=[{"at":"3.11.1","status":"unaffected"}]
  3. Affected versionversion=3.7.0 <=3.7.18 changes=[{"at":"3.7.19","status":"unaffected"}]
  4. Affected versionversion=3.8.0 <=3.8.11 changes=[{"at":"3.8.12","status":"unaffected"}]
  5. Affected versionversion=3.9.0 <=3.9.6 changes=[{"at":"3.9.7","status":"unaffected"}]

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Twitter · GitHub Enterprise Serverversion=3.10.0 <=3.10.3 changes=[{"at":"3.10.4","status":"unaffected"}]; version=3.11 <=3.11.0 changes=[{"at":"3.11.1","status":"unaffected"}]; version=3.7.0 <=3.7.18 changes=[{"at":"3.7.19","status":"unaffected"}]; version=3.8.0 <=3.8.11 changes=[{"at":"3.8.12","status":"unaffected"}]; version=3.9.0 <=3.9.6 changes=[{"at":"3.9.7","status":"unaffected"}]

Published CVSS scores

4.3NIST NVDCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
2.7GitHub, Inc.CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-863Incorrect Authorization
CAPEC-114Authentication Abuse
T1213.003Data from Information Repositories: Code Repositories

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo