64 matches found
SEDATED
El proyecto SEDATED® Sensitive Enterprise Data Analyzer To Eliminate Disclosure se centra en evitar que datos sensibles, como credenciales de usuario y tokens, se envíen a Git. Tabla de contenidos Propósito Configuración Clonar SEDATED® Actualizar los archivos .example Personalizar las variables ...
CVE-2026-3854
CVE-2026-3854: RCE en GitHub mediante inyección en el header X-Stat Resumen práctico de cómo funciona la vulnerabilidad descubierta por Wiz Research en el pipeline interno de git push de GitHub.com y GitHub Enterprise Server. Aviso Este material es con fines educativos y de investigación en...
CVE-2024-44625-Gogs-RCE-0.13.0
CVE-2024-44625 y Gogs-RCE-0.13.0 Validado contra una versión de Gogs de la era 0.13.0 detrás de un proxy inverso. Primitiva: el editor web sigue enlaces simbólicos hacia un archivo AUSENTE .git/hooks/pre-receive y crea ese archivo ejecutable. Cada push posterior al repositorio lo ejecuta. Uso:...
CVE-2025-81110-PoC
CVE-2025-81110-PoC El manejo inadecuado de enlaces simbólicos en la API PutContents de Gogs permite la ejecución local de código. Este repositorio contiene un exploit de nivel profesional para una vulnerabilidad crítica en versiones de Gogs anteriores a la 0.13.0. El exploit aprovecha una falla...
EUVD-2026-69716
A Server-Side Request Forgery SSRF vulnerability was identified in GitHub Enterprise Server that allowed remote code execution on the instance. Insufficient network isolation allowed malicious pre-receive hook code to impersonate an internal service and redirect trusted internal requests to a...
CVE-2026-76851
A Server-Side Request Forgery SSRF vulnerability was identified in GitHub Enterprise Server that allowed remote code execution on the instance. Insufficient network isolation allowed malicious pre-receive hook code to impersonate an internal service and redirect trusted internal requests to a...
CVE-2026-76851 Server-Side Request Forgery vulnerability in GitHub Enterprise Server allowed remote code execution via network access from pre-receive hooks to internal services
A Server-Side Request Forgery SSRF vulnerability was identified in GitHub Enterprise Server that allowed remote code execution on the instance. Insufficient network isolation allowed malicious pre-receive hook code to impersonate an internal service and redirect trusted internal requests to a...
CVE-2026-76851
A Server-Side Request Forgery (SSRF) vulnerability in GitHub Enterprise Server allowed remote code execution on the instance. The root cause was insufficient network isolation that permitted malicious pre-receive hook code to impersonate an internal service and redirect trusted internal requests ...
PT-2026-84532
Name of the Vulnerable Software and Affected Versions GitHub Enterprise Server versions prior to 3.22 Description A Server-Side Request Forgery SSRF issue exists where insufficient network isolation allows malicious pre-receive hook code to impersonate an internal service. This enables the...
GO-2026-6043 Gitea: Cached Per-Branch Permission Check in Pre-Receive Hook Allows Full Repository Write in code.gitea.io/gitea
Gitea: Cached Per-Branch Permission Check in Pre-Receive Hook Allows Full Repository Write in code.gitea.io/gitea...
EUVD-2026-41636
Gitea: Cached Per-Branch Permission Check in Pre-Receive Hook Allows Full Repository Write...
GHSA-649P-MMHF-85C7 Gitea: Cached Per-Branch Permission Check in Pre-Receive Hook Allows Full Repository Write
Vulnerability Header | Field | Value | | ------------------- | ----------------------------------------------------------------------------------- | | Vulnerability Title | Cached Per-Branch Permission Check in Pre-Receive Hook Allows Full Repository Write | | Severity Rating | High | | Bug...
Incorrect Authorization
Overview Affected versions of this package are vulnerable to Incorrect Authorization in the pre-receive process. An attacker can gain unauthorized write access to the entire repository by exploiting cached branch-specific write-permission results across multiple refs within a single session...
Incorrect Authorization
Overview Affected versions of this package are vulnerable to Incorrect Authorization in the pre-receive process. An attacker can gain unauthorized write access to the entire repository by exploiting cached branch-specific write-permission results across multiple refs within a single session...
Incorrect Authorization
Overview Affected versions of this package are vulnerable to Incorrect Authorization in the pre-receive process. An attacker can gain unauthorized write access to the entire repository by exploiting cached branch-specific write-permission results across multiple refs within a single session...
Incorrect Authorization
Overview Affected versions of this package are vulnerable to Incorrect Authorization in the pre-receive process. An attacker can gain unauthorized write access to the entire repository by exploiting cached branch-specific write-permission results across multiple refs within a single session...
Incorrect Authorization
Overview Affected versions of this package are vulnerable to Incorrect Authorization in the pre-receive process. An attacker can gain unauthorized write access to the entire repository by exploiting cached branch-specific write-permission results across multiple refs within a single session...
Incorrect Authorization
Overview Affected versions of this package are vulnerable to Incorrect Authorization in the pre-receive process. An attacker can gain unauthorized write access to the entire repository by exploiting cached branch-specific write-permission results across multiple refs within a single session...
Incorrect Authorization
Overview Affected versions of this package are vulnerable to Incorrect Authorization in the pre-receive process. An attacker can gain unauthorized write access to the entire repository by exploiting cached branch-specific write-permission results across multiple refs within a single session...
Incorrect Authorization
Overview Affected versions of this package are vulnerable to Incorrect Authorization in the pre-receive process. An attacker can gain unauthorized write access to the entire repository by exploiting cached branch-specific write-permission results across multiple refs within a single session...