View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0001149||Kali Linux||Queued Tool Addition||public||2014-04-12 09:23||2021-05-18 11:02|
|Priority||normal||Severity||minor||Reproducibility||have not tried|
|Fixed in Version||1.0.7|
fgdump was born out of frustration with current antivirus (AV) vendors who only partially handled execution of programs like pwdump. Certain vendors' solutions would sometimes allow pwdump to run, sometimes not, and sometimes lock up the box. As such, we as security engineers had to remember to shut off antivirus before running pwdump and similar utilities like cachedump. Needless to say, we're forgetful sometimes...
So fgdump started as simply a wrapper around things we had to do to make pwdump work effectively. Later, cachedump was added to the mix, as were a couple other variations of AV. Over time it has grown, and continues to grow, to support our assessments and other projects. We are beginning to use it extensively within Windows domains for broad password auditing, and in conjunction with other tools (ownr and pwdumpToMatrix.pl) for discovering implied trust relationships.
fgdump is targetted at the security auditing community, and is designed to be used for good, not evil. :) Note that, in order to effectively use fgdump, you're going to need high-power credentials (Administrator or Domain Administrator, in most cases), thus limiting its usefulness as a hacking tool. However, hopefully some of you other security folks will find this helpful.
|2014-04-12 09:23||g0tmi1k||New Issue|
|2014-04-15 19:34||dookie||Note Added: 0001702|
|2014-04-15 19:34||dookie||Status||new => resolved|
|2014-04-15 19:34||dookie||Fixed in Version||=> 1.0.7|
|2014-04-15 19:34||dookie||Resolution||open => fixed|
|2014-04-15 19:34||dookie||Assigned To||=> dookie|
||Issue cloned: 0001215|
|2021-05-18 11:02||g0tmi1k||Category||New Tool Requests => Queued Tool Addition|