View Issue Details

IDProjectCategoryView StatusLast Update
0006818Kali Linux[All Projects] Kali Package Bugpublic2021-09-14 20:20
Reporteriamthevic001 Assigned To 
Status closedResolutionsuspended 
Product Version2020.3 
Target VersionFixed in Version 
Summary0006818: Reverse shell on netcat does not provide command prompt
DescriptionWhen I exploit an issue and obtain a connect back via a reverse shell, I usually get a command prompt that allows me to move further ahead with the exploit. However, I updated the Kali package on 30-10-2020, and later found that I get the reverse shell upon a successful exploit, but I don't get a command prompt.

As a result of this I have to use the meterpreter payload and exploit the service.
Steps To ReproduceSteps to reproduce are as follows:
1. Identify a vulnerable service on a victim machine.
2. Generate a msfvenom shellcode using windows/shell/reverse_tcp as payload.
3. Keep a netcat listener ready.
4. Run the exploit with above payload.
5. The payload should produce a connect back on your netcat listener.
6. Observer that you don't have the command prompt.



2020-11-04 02:37

reporter   ~0013625

Are you specifying any level of verbosity with your netcat listener command?
I've had that issue when I didn't specify any.


2020-11-04 05:01

reporter   ~0013627

Yes. I use the nc -nlvp <add listening port> . But the issue is persisting.


2020-11-04 07:24

reporter   ~0013628

Have you tried not using the 'p' flag, since it's already listening locally & it seems kinda redundant?
sudo nc -vnl 8080
Which should listen on port 8080 on
Does it still crash?


2021-09-14 20:20

administrator   ~0015189

This report has been filed against an old version of Kali. We will be closing this ticket due to inactivity.
Please could you see if you are able to replicate this issue with the latest version of Kali Linux (
If you are still facing the same problem, feel free to re-open the ticket. If you choose to do this, could you provide more information to the issue you are facing, and also give information about your setup?
For more information, please read:

Issue History

Date Modified Username Field Change
2020-11-03 06:12 iamthevic001 New Issue
2020-11-04 02:37 TommyT Note Added: 0013625
2020-11-04 05:01 iamthevic001 Note Added: 0013627
2020-11-04 07:24 TommyT Note Added: 0013628
2020-12-01 10:48 g0tmi1k Priority urgent => normal
2020-12-01 10:50 g0tmi1k Severity crash => minor
2021-09-14 20:20 g0tmi1k Status new => closed
2021-09-14 20:20 g0tmi1k Resolution open => suspended
2021-09-14 20:20 g0tmi1k Note Added: 0015189