You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I realised that some defaults Windows accounts, like for example WDAGUtilityAccount, throw the following error:
However there is no error here. WDAGUtilisatyAccount does not have a NT hash in the SAM database because this is a virtual account used to contain applications in a sandbox (for example browsers) and these featuers are not used on windows servers. Considering I never saw secretsdump failing in dumping SAM database, I believe it is possible to switch the following liens from impacket/impacket/examples/secretsdump.py:
ifuserAccount['NTHashLength'] ==0:
logging.error('SAM hashes extraction for user %s failed. The account doesn\'t have hash information.'%userName)
continue
to
ifuserAccount['NTHashLength'] ==0:
logging.debug('SAM hashes extraction for user %s failed. The account doesn\'t have hash information.'%userName)
continue
That way most of tools using impacket secretsdump won't have a messed up output.
Let me know what you think about this :)
The text was updated successfully, but these errors were encountered:
Dfte
changed the title
SAM Dump for accoutns without secrets
SAM Dump for accounts without secrets
Oct 20, 2024
I realised that some defaults Windows accounts, like for example WDAGUtilityAccount, throw the following error:
However there is no error here. WDAGUtilisatyAccount does not have a NT hash in the SAM database because this is a virtual account used to contain applications in a sandbox (for example browsers) and these featuers are not used on windows servers. Considering I never saw secretsdump failing in dumping SAM database, I believe it is possible to switch the following liens from impacket/impacket/examples/secretsdump.py:
to
That way most of tools using impacket secretsdump won't have a messed up output.
Let me know what you think about this :)
The text was updated successfully, but these errors were encountered: