First published: Thu Dec 21 2023(Updated: )
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.
Credit: product-cna@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
GitHub Enterprise | >=3.7.0<3.7.19 | |
GitHub Enterprise | >=3.8.0<3.8.12 | |
GitHub Enterprise | >=3.9.0<3.9.7 | |
GitHub Enterprise | >=3.10.0<3.10.4 | |
GitHub Enterprise | =3.11.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2023-51379 is classified as medium due to the potential for unauthorized updates to issue comments.
To fix CVE-2023-51379, update your GitHub Enterprise Server to a version that provides the necessary security patch, such as 3.7.19 or higher.
CVE-2023-51379 affects GitHub Enterprise Server versions 3.7.0 to 3.7.19, 3.8.0 to 3.8.12, 3.9.0 to 3.9.7, 3.10.0 to 3.10.4, and 3.11.0.
CVE-2023-51379 is categorized as an incorrect authorization vulnerability.
No, CVE-2023-51379 does not allow unauthorized access to repository content, but it can permit unauthorized updates to issue comments.