dafthack / dafthack/MailSniper
Advice on succeeding with Invoke-DomainHarvestOWA?
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 3.3k
- Forks
- 597
- Avg merge
- 1h 11m
- Merged PRs (30d)
- 1
Description
Hey Beau,
Finally got a chance to use MailSniper on an engagement this week, and tried out the Invoke-DomainHarvest module with a list of about 8 domain names I thought would be possibly valid for the customer's environment. The module returned no valid domains, but later the customer confirmed that the valid domain was indeed one in my "guess" list. Are you aware of any tuning/protections/patches/etc. that could be in place from preventing MailSniper from identifying the valid domain through timing?
Also, I went one step further and tried the Invoke-UsernameHarvestOWA with a valid user (as well as a bunch of invalid users in the same file) and it was not identified as valid.
Thanks!
Brian / @7MinSec
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Invoke-DomainHarvest and Invoke-UsernameHarvestOWA entry points and compare their behavior with the reported valid and invalid domains and users. No file or test is named; reproduce the failures in a comparable Exchange/OWA environment and document a confirmed cause and fix or configuration guidance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100