🐛 Bug Report Template

🐛 Bug Report Template

Use this template when reporting bugs in AdPentestAI-Python. Please fill out all sections for faster resolution.

---

📋 Bug Description

What is the bug?
[Provide a clear, concise description of the issue]

Expected behavior:
[What should happen?]

Actual behavior:
[What actually happens?]

🔄 Steps to Reproduce

Environment:

• Python version: [e.g., 3.10, 3.11, 3.12]
• OS: [e.g., Linux, Windows, macOS]
• AdPentestAI version: [e.g., 1.0.2]

Command used:

python -m adpentest --target <target> --mode <mode> [options]

Step-by-step reproduction:

1. [First step]
2. [Second step]
3. [etc.]

📊 Error Output

Error message:

[Paste the full error message/traceback here]

Debug logs:

# Run with verbose output to capture debug info
python -m adpentest --target <target> --mode active --scope-confirmed 2>&1 | tee debug.log

[Paste relevant stderr output]

🎯 Impact

Severity: [Critical/High/Medium/Low]

• Critical: Tool crashes, data loss, security bypass
• High: Feature doesn't work, significant performance issue
• Medium: Workaround available, partial functionality
• Low: Minor cosmetic issue, documentation improvement

Affected tools: [e.g., nmap_scan, ldap_enum, email_server_discovery]

🔍 Additional Context

Network environment:

• Lab/Test environment
• Production environment
• Cloud environment (AWS/Azure/GCP)
• On-premises

Domain configuration:

• Domain name: [e.g., example.local]
• Domain functional level: [e.g., 2016, 2019, 2022]
• Forest level: [e.g., 2016, 2019]
• Number of DCs: [e.g., 2, 5, 10]

Network conditions:

• Direct network access to target
• Behind firewall/proxy
• High latency network (>100ms)
• Limited bandwidth

Have you tried?

• Running in dry-run mode first (--mode dry-run)
• With a different target
• On a different machine
• Updating to latest version
• Disabling custom DNS (--dns-server)

📎 Attachments

Configuration (if applicable):

# Redact sensitive information (IP addresses, domain names)
# Share anonymized config or command used

Sample output:

{
  "status": "partial",
  "environment": {...},
  "errors": [...]
}

Screenshots: [Attach any relevant screenshots]

🎓 Related Issues

• Relates to: [Link other issues if applicable]
• Duplicate of: [If this is a duplicate, link the original]
• Blocks: [If this blocks other work]

✅ Checklist

• I have searched existing issues (open & closed)
• I have tried the latest version
• I have tried dry-run mode (--mode dry-run)
• I have redacted sensitive information (IPs, usernames, domain names)
• I have included the full error message/traceback
• I have included Python version and OS information
• I have included the command used to trigger the bug
• I am running AdPentestAI with proper authorization

---

🚫 Before You Submit

Please DO NOT include:

• Real IP addresses, hostnames, or domain names
• Usernames, passwords, or credentials
• NTLM hashes, Kerberos tickets, or other sensitive credentials
• Internal network topology details
• Proprietary information

Replace with anonymized versions:

• 10.1.2.3 → 10.0.0.1
• corp.local → example.local
• user@corp.local → user@domain.local
• Full hashes → <NTLM_HASH> or <KRBTGT_HASH>

---

📝 Example Bug Report

📋 Bug Description

What is the bug?
LDAP RootDSE enumeration fails with timeout error when DC is in different subnet.

Expected behavior:
Should query DC's RootDSE successfully and extract domain information.

Actual behavior:
Tool times out after 10 seconds and reports "Connection refused" error.

🔄 Steps to Reproduce

Environment:

• Python version: 3.11
• OS: Ubuntu 22.04
• AdPentestAI version: 1.0.2

Command used:

python -m adpentest --target 10.0.0.50 --mode active --scope-confirmed --timeout 10

Step-by-step reproduction:

1. Run the command above
2. Tool attempts DC detection
3. Timeout occurs during LDAP RootDSE probe
4. Tool reports error and continues

📊 Error Output

Error message:

[VERBOSE] [probe_ldap_rootdse] Querying RootDSE on 10.0.0.50:389
[ERROR] LDAP probe failed: Socket timeout (10 seconds exceeded)
[VERBOSE] [detect_dcs] LDAP RootDSE probe failed, trying next strategy...

Debug logs:
[Output from python -m adpentest ... 2>&1 | grep LDAP]

🎯 Impact

Severity: Medium

• Tool falls back to other detection methods
• Workaround: Increase timeout with --dns-timeout 20
• Affected tool: enum_ldap, detect_dcs

🔍 Additional Context

Network environment:

• On-premises
• Network: 10.0.0.0/8 (DC on 10.0.0.50, attacker on 10.1.1.10)
• Latency: ~50ms between subnets

Domain configuration:

• Domain: example.local
• Domain functional level: 2019
• Number of DCs: 3

---

💬 Questions?

If you have questions about your issue:

1. Check the CLAUDE.md architecture documentation
2. Review CONTRIBUTING.md development guidelines
3. Open a GitHub Discussion: https://github.com/netanelcyber/AdPentestAI-Python/discussions

🎉 Thank You

Thank you for helping improve AdPentestAI-Python! Bug reports help make the framework more reliable for everyone.

The issue body is a complete bug-report template rather than a concrete change request, and it names no file or test to update. Read CLAUDE.md and CONTRIBUTING.md only if a specific template-maintenance task is clarified; completion criteria cannot be determined from the current report.