CVSS: 6.5EPSS: 0%CPEs: 4EXPL: 0CVE-2021-22861 – Improper access control in GitHub Enterprise Server leading to unauthorized write access to forkable repositories
https://notcve.org/view.php?id=CVE-2021-22861
An improper access control vulnerability was identified in GitHub Enterprise Server that allowed authenticated users of the instance to gain write access to unauthorized repositories via specifically crafted pull requests and REST API requests. An attacker would need to be able to fork the targeted repository, a setting that is disabled by default for organization owned private repositories. Branch protections such as required pull request reviews or status checks would prevent unauthorized commits from being merged without further review or validation. This vulnerability affected all versions of GitHub Enterprise Server since 2.4.21 and was fixed in versions 2.20.24, 2.21.15, 2.22.7 and 3.0.1. This vulnerability was reported via the GitHub Bug Bounty program. • https://docs.github.com/en/enterprise-server%402.20/admin/release-notes#2.20.24 https://docs.github.com/en/enterprise-server%402.21/admin/release-notes#2.21.15 https://docs.github.com/en/enterprise-server%402.22/admin/release-notes#2.22.7 https://docs.github.com/en/enterprise-server%403.0/admin/release-notes#3.0.1 • CWE-285: Improper Authorization •
CVSS: 8.8EPSS: 0%CPEs: 3EXPL: 0CVE-2020-10519 – Unsafe configuration options in GitHub Pages leading to remote code execution on GitHub Enterprise Server
https://notcve.org/view.php?id=CVE-2020-10519
A remote code execution vulnerability was identified in GitHub Enterprise Server that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.22.7 and was fixed in 2.22.7, 2.21.15, and 2.20.24. The underlying issues contributing to this vulnerability were identified through the GitHub Security Bug Bounty program. • https://docs.github.com/en/enterprise-server%402.20/admin/release-notes#2.20.24 https://docs.github.com/en/enterprise-server%402.21/admin/release-notes#2.21.15 https://docs.github.com/en/enterprise-server%402.22/admin/release-notes#2.22.7 • CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection') •
CVSS: 4.3EPSS: 0%CPEs: 3EXPL: 0CVE-2020-10517 – Improper access control in GitHub Enterprise Server leading to the enumeration of private repository names
https://notcve.org/view.php?id=CVE-2020-10517
An improper access control vulnerability was identified in GitHub Enterprise Server that allowed authenticated users of the instance to determine the names of unauthorized private repositories given their numerical IDs. This vulnerability did not allow unauthorized access to any repository content besides the name. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.22 and was fixed in versions 2.21.6, 2.20.15, and 2.19.21. This vulnerability was reported via the GitHub Bug Bounty program. Se identificó una vulnerabilidad de control de acceso inapropiado en GitHub Enterprise Server que permitió a usuarios autenticados de la instancia determinar los nombres de los repositorios privados no autorizados dados sus ID numéricos. • https://enterprise.github.com/releases/2.19.21/notes https://enterprise.github.com/releases/2.20.15/notes https://enterprise.github.com/releases/2.21.6/notes • CWE-285: Improper Authorization •
CVSS: 8.8EPSS: 0%CPEs: 3EXPL: 0CVE-2020-10518 – Unsafe configuration options in GitHub Pages leading to remote code execution on GitHub Enterprise Server
https://notcve.org/view.php?id=CVE-2020-10518
A remote code execution vulnerability was identified in GitHub Enterprise Server that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.22 and was fixed in 2.21.6, 2.20.15, and 2.19.21. The underlying issues contributing to this vulnerability were identified both internally and through the GitHub Security Bug Bounty program. • https://enterprise.github.com/releases/2.19.21/notes https://enterprise.github.com/releases/2.20.15/notes https://enterprise.github.com/releases/2.21.6/notes • CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection') •
CVSS: 9.8EPSS: 1%CPEs: 2EXPL: 1CVE-2017-18365
https://notcve.org/view.php?id=CVE-2017-18365
The Management Console in GitHub Enterprise 2.8.x before 2.8.7 has a deserialization issue that allows unauthenticated remote attackers to execute arbitrary code. This occurs because the enterprise session secret is always the same, and can be found in the product's source code. By sending a crafted cookie signed with this secret, one can call Marshal.load with arbitrary data, which is a problem because the Marshal data format allows Ruby objects. La consola de gestión en GitHub Enterprise, en las versiones 2.8.x anteriores a la 2.8.7, tiene un fallo de deserialización que permite a los atacantes remotos sin autenticar ejecutar código arbitrario. Esto ocurre debido a que el secreto de sesión "enterprise" es siempre el mismo y puede encontrarse en el código fuente del producto. • https://enterprise.github.com/releases/2.8.7/notes https://www.exablue.de/blog/2017-03-15-github-enterprise-remote-code-execution.html • CWE-502: Deserialization of Untrusted Data •