dafthack / dafthack/MailSniper

o365 mail sniffering feature : relam based site

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

Nobody has claimed this yet.

bug
Dominant language
PowerShell
Stars
3.3k
Forks
597
Avg merge
1h 11m
Merged PRs (30d)
1

Description

Hi, i was testing the feature of owa bypass. And when i targeted i got the prompt for username and password, however with correct user name pass also its asked again and again. And also if i try to run the invoke self search command its not working. The domain used in the environment looks like below. Please help me on this.
The actual owa site is like: outlook.office.com/owa/?realm=xxx.com
On browser:
https://outlook.office365.com/EWS/Exchange.asmx/relam=xxx.com ---> This asked for username and password again and again.

I used the below command on mailsniper module:
i tested couple of options with no results.
PS C:> Invoke-SelfSearch -Mailbox aaabbb@domainxxx.com -ExchHostname outloo
k.office365.com Remote

PS C:> Invoke-SelfSearch -Mailbox aaabbb@domainxxx.com -ExchHostname https:
//outlook.office365.com/EWS/Exchange.asmx/relam=xxx.com Remote

Error:
Exception calling "Bind" with "2" argument(s): "The request failed. The remote
server returned an error: (404) Not Found."
At C:\MailSniper.ps1:778 char:73

  •     $rootFolder = [Microsoft.Exchange.WebServices.Data.Folder]::Bind <<<<
    

($service,$FolderId)
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : DotNetMethodException
Let me know.

Contributor guide

No contributing guide indexed for this repository

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 with Invoke-SelfSearch in MailSniper.ps1 around line 778 and reproduce the reported 404 using the listed ExchHostname and realm-based URLs. Confirm whether the issue is with the supplied Exchange endpoint or the feature's handling of realm-based sites; done would require a defined, working search flow for the reported environment.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell
Domain
security, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.