Ensure webhooks of the repository are secured

HighLevel 1Automatedgithub

Description

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.

How it is checked

Audit method: Shell command

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

Expected output: compliant

How it is fixed

Fix method: Guidance or infrastructure patch

Edit each listed repository webhook (Settings > Webhooks) to use https:// with SSL verification and a secret.

Properties

Operating systems: Any
Tags: githubartifacts
Reference: CIS GitHub Benchmark v1.2.0 - 4.3.4 Ensure webhooks of the repository are secured

Check this host

Run this on a machine you are allowed to audit. The scan is read-only.

shell

tmaegis scan --target github