Page 14 of 82 results (0.008 seconds)

CVSS: 7.2EPSS: 0%CPEs: 4EXPL: 0

An incorrect authorization vulnerability was identified in GitHub Enterprise Server that allowed a scoped user-to-server token to escalate to full admin/owner privileges. An attacker would require an account with admin access to install a malicious GitHub App. This vulnerability was fixed in versions 3.3.17, 3.4.12, 3.5.9, and 3.6.5. This vulnerability was reported via the GitHub Bug Bounty program. Se identificó una vulnerabilidad de autorización incorrecta en GitHub Enterprise Server que permitió que un token de usuario a servidor con alcance escalara a privilegios completos de administrador/propietario. • https://docs.github.com/en/enterprise-server%403.3/admin/release-notes#3.3.17 https://docs.github.com/en/enterprise-server%403.4/admin/release-notes#3.4.12 https://docs.github.com/en/enterprise-server%403.5/admin/release-notes#3.5.9 https://docs.github.com/en/enterprise-server%403.6/admin/release-notes#3.6.5 • CWE-863: Incorrect Authorization •

CVSS: 9.8EPSS: 0%CPEs: 1EXPL: 0

An improper limitation of a pathname to a restricted directory vulnerability was identified in GitHub Enterprise Server that enabled remote code execution. A check was added within Pages to ensure the working directory is clean before unpacking new content to prevent an arbitrary file overwrite bug. This vulnerability affected only version 3.7.0 of GitHub Enterprise Server and was fixed in version 3.7.1. This vulnerability was reported via the GitHub Bug Bounty program. Se identificó una limitación inadecuada de un nombre de ruta a una vulnerabilidad de directorio restringido en GitHub Enterprise Server que permitía la ejecución remota de código. • https://docs.github.com/en/enterprise-server%403.7/admin/release-notes#3.7.1 • CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') •

CVSS: 6.5EPSS: 0%CPEs: 5EXPL: 0

An improper privilege management vulnerability was identified in GitHub Enterprise Server that allowed users with improper privileges to create or delete pages via the API. To exploit this vulnerability, an attacker would need to be added to an organization's repo with write permissions. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.7 and was fixed in versions 3.2.20, 3.3.15, 3.4.10, 3.5.7, and 3.6.3. This vulnerability was reported via the GitHub Bug Bounty program. Se identificó una vulnerabilidad de administración de privilegios inadecuada en GitHub Enterprise Server que permitía a los usuarios con privilegios inadecuados crear o eliminar páginas a través de la API. • https://docs.github.com/en/enterprise-server%403.2/admin/release-notes#3.2.20 https://docs.github.com/en/enterprise-server%403.3/admin/release-notes#3.3.15 https://docs.github.com/en/enterprise-server%403.4/admin/release-notes#3.4.10 https://docs.github.com/en/enterprise-server%403.5/admin/release-notes#3.5.7 https://docs.github.com/en/enterprise-server%403.6/admin/release-notes#3.6.3 • CWE-269: Improper Privilege Management •

CVSS: 8.8EPSS: 0%CPEs: 1EXPL: 0

CRITICAL: An improper neutralization of argument delimiters in a command vulnerability was identified in GitHub Enterprise Server that enabled remote code execution. To exploit this vulnerability, an attacker would need permission to create and build GitHub Pages using GitHub Actions. This vulnerability affected only version 3.7.0 of GitHub Enterprise Server and was fixed in version 3.7.1. This vulnerability was reported via the GitHub Bug Bounty program. CRÍTICO: Se identificó una neutralización incorrecta de los delimitadores de argumentos en una vulnerabilidad de comando en GitHub Enterprise Server que permitía la ejecución remota de código. • https://docs.github.com/en/enterprise-server%403.7/admin/release-notes#3.7.1 • CWE-88: Improper Neutralization of Argument Delimiters in a Command ('Argument Injection') •

CVSS: 5.7EPSS: 0%CPEs: 5EXPL: 0

An improper cache key vulnerability was identified in GitHub Enterprise Server that allowed an unauthorized actor to access private repository files through a public repository. To exploit this, an actor would need to already be authorized on the GitHub Enterprise Server instance, be able to create a public repository, and have a site administrator visit a specially crafted URL. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.6 and was fixed in versions 3.2.20, 3.3.15, 3.4.10, 3.5.7, 3.6.3. This vulnerability was reported via the GitHub Bug Bounty program. Se identificó una vulnerabilidad de clave de caché inadecuada en GitHub Enterprise Server que permitió a un actor no autorizado acceder a archivos del repositorio privado a través de un repositorio público. • https://docs.github.com/en/enterprise-server%403.2/admin/release-notes#3.2.20 https://docs.github.com/en/enterprise-server%403.3/admin/release-notes#3.3.15 https://docs.github.com/en/enterprise-server%403.4/admin/release-notes#3.4.10 https://docs.github.com/en/enterprise-server%403.5/admin/release-notes#3.5.7 https://docs.github.com/en/enterprise-server%403.6/admin/release-notes#3.6.3 • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor CWE-552: Files or Directories Accessible to External Parties •