netanelcyber / netanelcyber/AdPentestAI-Python

Feature: Add support for Exchange Server enumeration

Open
#25 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement exchange-server feature-request
Dominant language
Python
Stars
5
Forks
2
Avg merge
22h 25m
Merged PRs (30d)
7

Description

Feature Request: Exchange Server Enumeration

Description

Add comprehensive Exchange Server enumeration capabilities including:

  • Version detection (2013, 2016, 2019, 2021, O365)
  • Outlook Web Access (OWA) discovery
  • Autodiscover service probing
  • Mailbox enumeration
  • Distribution list enumeration
  • ProxyLogon vulnerability scanning
Motivation

Exchange Server is a critical component in many AD environments and is frequently targeted in attacks. Comprehensive enumeration is essential for thorough security assessments.

Related CVEs
  • CVE-2021-26855 (ProxyLogon SSRF)
  • CVE-2021-27065 (ProxyLogon File Write)
  • CVE-2021-26857 (ProxyLogon PostAuth RCE)
  • CVE-2021-26858 (ProxyLogon Escalation)
Acceptance Criteria
  • Exchange version detection
  • OWA discovery and fingerprinting
  • Autodiscover enumeration
  • Mailbox listing capability
  • ProxyLogon vulnerability checks
  • Integration with main AD scan
Implementation Notes
  • Use EWS API where possible
  • Fallback to HTTP fingerprinting
  • Add to parallel execution pipeline

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the main AD scan and its parallel execution pipeline, then determine how Exchange Server enumeration should integrate with them. Use the acceptance criteria to scope version detection, OWA and Autodiscover probing, mailbox and distribution-list enumeration, and ProxyLogon checks. Done means each listed capability is integrated and verified without compromising the existing scan flow.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.