Skip to content

VNX-GH-216: Webhook deliveries can be forged or intercepted

A repository webhook has no secret, or disables TLS verification.

Updated 02 Nov 2026Checked against cli@24498404a, vdb-sca-match@v0.8.14

Webhooks often drive deployments. Without a signing secret anyone can forge an event; without TLS verification the payload (and anything it triggers) can be intercepted or altered.

Severity Medium
Confidence high
CWE CWE-345, CWE-295
Command vulnetix gha settings, vulnetix gha audit
Needs webhooks. Without them the rule is reported as not evaluated, never as passed.

Remediation

Set a webhook secret and verify X-Hub-Signature-256 on receipt; enable SSL verification.

Run only this rule

vulnetix gha settings --rule VNX-GH-216

Scoring

CWSS vector at the rule’s default severity: CWSS:1.0/TI:M/AP:A/AL:A/IC:N/FC:LT/RP:N/RL:A/AV:I/AS:N/IN:A/SC:A/BI:M/DI:M/EX:M/EC:N/P:W. A finding whose severity the repository’s settings moved is scored at its adjusted severity.

All rules: GitHub rules.

Edit this pageSources: vdb-sca-match/ghaudit/rules_settings.go, cli/internal/ghtasks/docs.go
esc
↑ ↓ move↵ openSearches in your browser. A key like autonomy.max or a code like threshold_required jumps straight to it.