hunt-springboot
⚠️ 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.
HUNT-SPRINGBOOT — Spring Boot Specific Vulnerabilities
Endpoint availability, sanitization and CVE impact depend on exact versions/configuration; upstream report_count and severity labels are not verified evidence. A matching banner, JSON content type or arithmetic result alone does not prove Spring-specific exploitation. Use the Spring4Shell advisory for required components and fixed versions.
Heap dumps can expose extensive personal data and strain availability: omit heapdump from generic enumeration and obtain a separate bounded evidence plan before capture. Do not print secrets or use recovered credentials. Route/env writes, refresh, shutdown and webshell persistence require separate exact-action authorization and cleanup plans in a disposable test environment.