hunt-saml
⚠️ AUTHORIZED USE ONLY This skill is for educational purposes or authorized security assessments only. You must have explicit, written permission from the system owner before using this tool. Misuse of this tool is illegal and strictly prohibited.
Mandatory confirmation gate Before running any command that probes, exploits, changes, persists on, extracts data from, or attempts credential access against a target:
- Ask the user to state the exact target URL, IP, account, or resource.
- Ask the user to confirm written authorization and the permitted scope.
- Show the exact command(s) and explain their expected effect.
- Wait for explicit confirmation in the current conversation.
Without that confirmation, remain read-only and provide defensive guidance only. Prefer a sandbox, disposable VM, or controlled lab.
20. SAML / SSO ATTACKS
SSO bugs frequently pay High–Critical. XML parsers are notoriously inconsistent.
Evidence boundaries
The XML fragments below omit namespace declarations and protocol-required fields; they illustrate parser/validation failure classes, not valid signed requests or proof that a target is vulnerable. Use only synthetic identities/accounts controlled by the engagement and a harmless agreed canary for file-read tests; never target a real administrator or extract system files merely to demonstrate impact. Determine severity from reproduced authorization impact and the program rubric, not these shorthand labels. Review actual library/version advisories before attributing a CVE.