Vulnerability Monitor

The vendors, products, and vulnerabilities you care about

CVE-2023-51379

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.

Security Impact Summary

This vulnerability carries a MEDIUM severity rating with a CVSS v3.1 score of 4.9, indicating it can be exploited remotely over the network with relatively low complexity without requiring user interaction . The vulnerability impacts integrity (unauthorized modifications), for affected systems. Impacting 1 product from github organizations running these solutions should prioritize assessment and patching.

Historical Context

Reported in 2023, this vulnerability emerged during an era marked by increased sophistication in supply chain attacks, cloud infrastructure vulnerabilities, and software-as-a-service (SaaS) security challenges. Security practices during this period emphasized zero-trust architectures, container security, and API protection.

Published

2023-12-21T21:15:13.480

Last Modified

2024-12-16T19:07:10.117

Status

Analyzed

Source

[email protected]

Severity

CVSSv3.1: 4.9 (MEDIUM)

Weaknesses

Type: Secondary
CWE-863
Type: Primary
CWE-863

Affected Vendors & Products

Type	Vendor	Product	Version/Range	Vulnerable?
Application	github	enterprise_server	< 3.7.19	Yes
Application	github	enterprise_server	< 3.8.12	Yes
Application	github	enterprise_server	< 3.9.7	Yes
Application	github	enterprise_server	< 3.10.4	Yes
Application	github	enterprise_server	3.11.0	Yes

References

https://docs.github.com/en/[email protected]/admin/release-notes#3.10.4 Release Notes ([email protected])
https://docs.github.com/en/[email protected]/admin/release-notes#3.11.1 Release Notes ([email protected])
https://docs.github.com/en/[email protected]/admin/release-notes#3.7.19 Release Notes ([email protected])
https://docs.github.com/en/[email protected]/admin/release-notes#3.8.12 Release Notes ([email protected])
https://docs.github.com/en/[email protected]/admin/release-notes#3.9.7 Release Notes ([email protected])
https://docs.github.com/en/[email protected]/admin/release-notes#3.10.4 Release Notes (af854a3a-2127-422b-91ae-364da2661108)
https://docs.github.com/en/[email protected]/admin/release-notes#3.11.1 Release Notes (af854a3a-2127-422b-91ae-364da2661108)
https://docs.github.com/en/[email protected]/admin/release-notes#3.7.19 Release Notes (af854a3a-2127-422b-91ae-364da2661108)
https://docs.github.com/en/[email protected]/admin/release-notes#3.8.12 Release Notes (af854a3a-2127-422b-91ae-364da2661108)
https://docs.github.com/en/[email protected]/admin/release-notes#3.9.7 Release Notes (af854a3a-2127-422b-91ae-364da2661108)

How SecUtils Interprets This CVE

SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For github's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.