GitHub
TMA-GITHUB-4.3.4
Ensure webhooks of the repository are secured
Descripción
Use secured webhooks to reduce the possibility of malicious payloads. Webhooks are used for triggering an HTTP request based on an action made in the platform. Typically, package registries feature webhooks when a package receives an update. Every repository webhook must use an https:// URL with SSL verification enabled (insecure_ssl 0). Uses the GitHub REST/GraphQL API through gh api (read-only). The repository comes from GH_REPO or the current git checkout (gh's {owner}/{repo} resolution, GH_HOST for GitHub Enterprise Server); the organization comes from GH_ORG (default: the repository owner). Fails when gh is missing or unauthenticated (gh auth login or GH_TOKEN); organization settings and branch protection need an owner/admin token.
Cómo se verifica
Método de auditoría: Comando de shell
command -v gh >/dev/null 2>&1 || exit 1
gh auth status >/dev/null 2>&1 || exit 1
info=$(gh api 'repos/{owner}/{repo}' --jq '.full_name + " " + .default_branch' 2>/dev/null) || exit 1
R=${info% *}; B=${info#* }
[ -n "$R" ] && [ -n "$B" ] || exit 1
rh=$(gh api --paginate "repos/$R/hooks?per_page=100" --jq '.[] | select(((.config.url // "") | startswith("https://") | not) or ((.config.insecure_ssl // "0") | tostring) != "0") | (.config.url // "?")' 2>/dev/null) || exit 1
b=$(printf '%s\n' "$rh" | grep . || true)
[ -z "$b" ] && echo compliant || printf 'insecure webhook: %s\n' $b- Salida esperada
compliant
Cómo se corrige
Método de corrección: Guía o parche de infraestructura
Edit each listed repository webhook (Settings > Webhooks) to use https:// with SSL verification and a secret.
Propiedades
- Sistemas operativos
- Cualquiera
- Etiquetas
- githubartifacts
- Referencia
- CIS GitHub Benchmark v1.2.0 - 4.3.4 Ensure webhooks of the repository are secured
Verificar este host
Ejecute esto en un equipo que tenga permiso para auditar. El escaneo es de solo lectura.
tmaegis scan --target github