Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/dafthack/MFASweep
A tool for checking if MFA is enabled on multiple Microsoft Services
https://github.com/dafthack/MFASweep
Last synced: about 1 month ago
JSON representation
A tool for checking if MFA is enabled on multiple Microsoft Services
- Host: GitHub
- URL: https://github.com/dafthack/MFASweep
- Owner: dafthack
- License: mit
- Created: 2020-09-22T16:25:03.000Z (about 4 years ago)
- Default Branch: master
- Last Pushed: 2024-09-24T21:28:26.000Z (3 months ago)
- Last Synced: 2024-10-29T15:40:11.159Z (about 1 month ago)
- Language: PowerShell
- Size: 1.33 MB
- Stars: 1,368
- Watchers: 25
- Forks: 186
- Open Issues: 15
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
- awesome-cloud-security - 地址
- Awesome-Azure-Pentest - MFASweep - A tool for checking if MFA is enabled on multiple Microsoft Services Resources (Tools / Exploitation)
README
# MFASweep
MFASweep is a PowerShell script that attempts to log in to various Microsoft services using a provided set of credentials and will attempt to identify if MFA is enabled. Depending on how conditional access policies and other multi-factor authentication settings are configured some protocols may end up being left single factor. It also has an additional check for ADFS configurations and can attempt to log in to the on-prem ADFS server if detected.
Currently MFASweep has the ability to login to the following services:
* Microsoft Graph API
* Azure Service Management API
* Microsoft 365 Exchange Web Services
* Microsoft 365 Web Portal w/ 6 device types (Windows, Linux, MacOS, Android Phone, iPhone, Windows Phone)
* Microsoft 365 Active Sync
* ADFS
**WARNING: This script attempts to login to the provided account TEN (10) different times (11 if you include ADFS). If you entered an incorrect password this may lock the account out.**
For more information check out the blog post here: [Exploiting MFA Inconsistencies on Microsoft Services](https://www.blackhillsinfosec.com/exploiting-mfa-inconsistencies-on-microsoft-services/)
## Usage
This command will use the provided credentials and attempt to authenticate to the Microsoft Graph API, Azure Service Management API, Microsoft 365 Exchange Web Services, Microsoft 365 Web Portal with both a desktop browser and mobile, and Microsoft 365 Active Sync. If any authentication methods result in success, tokens and/or cookies will be written to AccessTokens.json. (Currently does not log cookies or tokens for EWS, ActiveSync, and ADFS)
```PowerShell
Invoke-MFASweep -Username [email protected] -Password Winter2024 -WriteTokens
```
This command runs with the default auth methods and checks for ADFS as well.
```PowerShell
Invoke-MFASweep -Username [email protected] -Password Winter2020 -Recon -IncludeADFS
```
## Individual Modules
Each individual module can be run separately if needed as well.
**Microsoft Graph API**
```PowerShell
Invoke-GraphAPIAuth -Username [email protected] -Password Winter2020
```
**Azure Service Management API**
```PowerShell
Invoke-AzureManagementAPIAuth -Username [email protected] -Password Winter2020
```
**Microsoft 365 Exchange Web Services**
```PowerShell
Invoke-EWSAuth -Username [email protected] -Password Winter2020
```
**Microsoft 365 Web Portal**
```PowerShell
Invoke-O365WebPortalAuth -Username [email protected] -Password Winter2020
```
**Microsoft 365 Web Portal w/ Mobile User Agent**
```PowerShell
Invoke-O365WebPortalAuthMobile -Username [email protected] -Password Winter2020
```
**Microsoft 365 Active Sync**
```PowerShell
Invoke-O365ActiveSyncAuth -Username [email protected] -Password Winter2020
```
**ADFS**
```PowerShell
Invoke-ADFSAuth -Username [email protected] -Password Winter2020
```
### Brute Forcing Client IDs During ROPC Auth
The Invoke-BruteClientIDs function will loop through various resource types and client IDs during ROPC auth to find single factor access for various combinations of client IDs and resources. If any authentication methods result in success, tokens and/or cookies will be written to AccessTokens.json. (Currently does not log cookies or tokens for EWS, ActiveSync, and ADFS)
```PowerShell
Invoke-BruteClientIDs -Username [email protected] -Password Winter2024 -WriteTokens
```