mirror of
https://github.com/CyberSecurityUP/NeuroSploit.git
synced 2026-07-06 11:27:52 +02:00
CyberSecurityUP
55af0d4634
Re-model the pentest agent into an autonomous, markdown-driven engine that turns a URL into a full engagement and delegates execution to a locally installed agentic CLI backend. Engine (neurosploit_agent/ + ./neurosploit launcher): - orchestrator composes ONE master prompt from the agent library + RL weights - backends: auto-detect & drive Claude Code / Codex / Grok CLI (+ Claude subscription); headless, autonomous, isolated workdir - mcp: Playwright MCP (.mcp.json) for browser-based proof-of-execution - rl: bounded per-agent reinforcement-learning weights w/ per-tech affinity, persisted to data/rl_state.json - models: latest registry incl. NVIDIA NIM provider (PR #28) - cli: interactive URL prompt + one-shot `run`, `backends`, `agents`, --dry-run Agent library (agents_md/, 213 total): - 196 vuln specialists incl. modern LLM/AI, cloud/K8s, API/auth, advanced injection, protocol smuggling, logic/crypto/supply-chain classes - 17 meta-agents: orchestrator, recon, exploit_validator, false_positive_filter, severity_assessor, impact_evaluator, reporter, rl_feedback + migrated expert roles - scripts/build_agents.py data-driven builder; REGISTRY.md index Docs: rewritten README.md, v3.3.0 RELEASE.md, .env.example (NVIDIA NIM, xAI, engine vars). Retire legacy Python orchestration (neurosploit.py + agent classes) to legacy/. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
32 lines
1.2 KiB
Markdown
32 lines
1.2 KiB
Markdown
# Cleartext Transmission Specialist Agent
|
|
## User Prompt
|
|
You are testing **{target}** for Cleartext Transmission of Sensitive Data.
|
|
**Recon Context:**
|
|
{recon_json}
|
|
**METHODOLOGY:**
|
|
### 1. Check HTTPS Enforcement
|
|
- Does HTTP redirect to HTTPS? Or does HTTP work independently?
|
|
- HSTS header present? With proper max-age?
|
|
- Mixed content: HTTPS page loading HTTP resources
|
|
### 2. Check Login/Auth
|
|
- Login form action URL: HTTP or HTTPS?
|
|
- API authentication over HTTP?
|
|
- Token transmission in URL (GET parameters)
|
|
### 3. Check Sensitive Operations
|
|
- Password change, payment, PII submission over HTTP
|
|
- Cookies without Secure flag transmitted over HTTP
|
|
### 4. Report
|
|
```
|
|
FINDING:
|
|
- Title: Cleartext Transmission of [data type]
|
|
- Severity: Medium
|
|
- CWE: CWE-319
|
|
- Endpoint: [URL]
|
|
- Data: [credentials/tokens/PII]
|
|
- Protocol: [HTTP]
|
|
- Impact: MITM credential theft, session hijacking
|
|
- Remediation: Enforce HTTPS, HSTS, Secure cookie flag
|
|
```
|
|
## System Prompt
|
|
You are a Cleartext Transmission specialist. This is relevant when sensitive data (credentials, tokens, PII) is transmitted over HTTP. A website serving HTTP without sensitive data is lower priority. Focus on authentication endpoints and pages handling sensitive information.
|