byt3bl33d3r / CrackMapExec

A swiss army knife for pentesting networks
BSD 2-Clause "Simplified" License
8.35k stars 1.64k forks source link

Crackmapexec using poetry and proxychains not working #767

Closed Rffrench closed 1 year ago

Rffrench commented 1 year ago

Describe the bug Hey there, I have been trying to run crackmapexec with proxychains and poetry using every kind of combination but there seems to be a bug in proxychains, poetry or crackmapexec. Every other tool I use with `proxychains``works perfectly.

Here are the different ways I have tried executing it. Note again that if I use proxychains with nmap or other tools it works just fine.

CrackmapExec is in the cme folder and it works fine when executing it without proxychains.

Expecting value: line 1 column 2 (char 1)


- Method 2 (`poetry` with absolute path):
```bash
chino@mypc:~/Applications/cme$ proxychains /home/chino/.local/bin/poetry run crackmapexec
[proxychains] config file found: /etc/proxychains4.conf
[proxychains] preloading /usr/lib/x86_64-linux-gnu/libproxychains.so.4
[proxychains] DLL init: proxychains-ng 4.14

Expecting value: line 1 column 2 (char 1)

Expecting value: line 1 column 2 (char 1)



**To Reproduce**
Steps to reproduce the behavior:
1. Install crackmapexec following the official wiki instructions (`poetry` way)
2. Install proxychains-ng
3. In the CME folder created, run `proxychains poetry run crackmapexec`

**Expected behavior**
Working normally.

**Crackmapexec info**
OS: `Ubuntu 20.04.1`
 - Version of CME Version : 5.4.1
 - Installed from apt or using latest release ? Installed manually with latest release

I would highly appreciate any help!
Thanks in advance
Rffrench commented 1 year ago

Fixed it. poetry had a bug that caused errors with proxychains and it got fixed with the latest versions.