-
Notifications
You must be signed in to change notification settings - Fork 75
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
Azurehound runs out of memory during data collection #32
Comments
This issue appears to be a duplicate to #6 . However, I didn't receive any error aside from zsh reporting that the process was killed. Had to dig into the system messages in order to figure out that it was specifically an out of memory error. |
Although that bash command didn't resolve the issue, it did help me collect a significant amount of the azurehound data. This issue is probably present with all submodules to the list command, but I suspect the az-ad and az-rm modules are the submodules that are most likely to cause the issue. |
Any updates on this Issue? Find here the according stack-trace:
|
Ok, we were able to resolve the issue (kind of): |
We believe that this should be resolved as of https://github.com/BloodHoundAD/AzureHound/releases/tag/v2.1.5. Can you please test again and let us know if this remains an ongoing issue? |
Performing an
azurehound list
command against very large azure deployments triggers oom-killer in kali linux, which causes the process to die. It dies shortly after the service principal owner enumeration (so likely the az-ad enum?). Tried to enumerate each tenant separately but couldn't figure out how to do so. Instead, I decided to enumerate based on each available method for the list command. Not sure if this will work, but the command I am attempting to use to accomplish the task is as follows:This might work as a short term solution, but a long term fix for this issue is definitely needed.
The text was updated successfully, but these errors were encountered: