-
Notifications
You must be signed in to change notification settings - Fork 267
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AAD report error due to invalid JSON result #1607
Comments
Hey @Strawberryww, thanks for reporting this issue. We have replicated the bug and are looking into a fix. Are you seeing any results for the |
@mitchelbaker-cisa Thanks. Yes, there is result for the |
I created a new branch that adds additional error handling to the Do you mind downloading a zip of the new branch to test out the fix? It can be found here: After importing it in a new PowerShell terminal, run |
@mitchelbaker-cisa Thanks for your analysis. I've tried the fix with
![]() There is value for ![]() I've double checked that the code ![]() Is there any way to save the output to a file before converting to JSON? Then, it's better for analysis. That is:
Thanks. |
🐛 Summary
When using ScubaGear 1.5.0 to scan AAD, it reports the following error:
To reproduce
My Azure tenant can always reproduces the error, but another tenant is OK.
The invoke command is as below:
Env:
ScubaGear: 1.5.0
Powershell: 5.1.19041.5369
Windows 10 Pro: 10.0.19045 N/A Build 19045
Expected behavior
There should be no such error.
Any helpful log output or screenshots
The generated JSON result is as below:
The
risky_third_party_service_principals
field is missing its value.Possibly the error is related to the following code in
PowerShell/ScubaGear/Modules/Providers/ExportAADProvider.psm1
:Error in PowerShell:
The text was updated successfully, but these errors were encountered: