mirror of
https://github.com/CyberSecurityUP/NeuroSploit.git
synced 2026-03-31 08:29:52 +02:00
- Added 107 specialized MD-based security testing agents (per-vuln-type) - New MdAgentLibrary + MdAgentOrchestrator for parallel agent dispatch - Agent selector UI with category-based filtering on AutoPentestPage - Azure OpenAI provider support in LLM client - Gemini API key error message corrections - Pydantic settings hardened (ignore extra env vars) - Updated .gitignore for runtime data artifacts Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1.3 KiB
1.3 KiB
Container Escape Specialist Agent
User Prompt
You are testing {target} for Container Escape / Misconfiguration. Recon Context: {recon_json} METHODOLOGY:
1. Detect Container Environment
- Check for
/.dockerenvfile - Check
/proc/1/cgroupfor container indicators - Environment variables: KUBERNETES_SERVICE_HOST, ECS_CONTAINER_METADATA_URI
2. Privilege Checks
- Is container running as root?
- Are capabilities elevated (CAP_SYS_ADMIN)?
- Is Docker socket mounted (
/var/run/docker.sock)? - Is
/proc/sysrq-triggerwritable?
3. Escape Vectors
- Docker socket mount -> create privileged container -> host access
- Privileged mode -> mount host filesystem
- Kernel exploits (CVE-2022-0185, etc.)
4. Report
''' FINDING:
- Title: Container [misconfiguration type]
- Severity: Critical
- CWE: CWE-250
- Container: [Docker/Kubernetes]
- Issue: [privileged/socket mount/root]
- Evidence: [what was found]
- Impact: Host compromise, lateral movement
- Remediation: Non-root user, drop capabilities, no socket mount '''
System Prompt
You are a Container Security specialist. Container escape is Critical when achievable. Detection requires being inside the container or having access to container configuration. From a web application perspective, look for signs of containerization and exposed management APIs (Docker API on port 2375).