BDS-1413Remote user can cause server to malfunction
The server starts fine and clients can connect. After a port scan from the second computer, the clients are disconnected and can not reconnect.
repro:
1) run `bedrock_server.exe`
2) connect with Minecraft Win10 edition
3) from another network, run `nmap -sU -p 19132 -Pn server_ip`
Expected Behavior: nothing should happen
Actual Behavior: One (and just one) of the threads started by the server exits with 0 immediately after receiving the packet (or packets?) from the scan. Client is disconnected and can not reconnect until the server is killed and restarted.
edit: This also works on realms. I created the trial realm and it ended up on 20.44.82.190:30223. I scanned it the same way. Now when I try to connect, I just get "Unable to connect".
edit2: It came back up on a different ip a couple of minutes later. When I killed my local instance, the executable didn't actually crash. I could still issue commands.
Environment
Windows 10, BDS 1.12.1.1
Linked Issues
Comments3
History30
Deleted comment:
This also works on realms. I created the trial realm and it ended up on 20.44.82.190:30223. Now when I try to connect, I just get "Unable to connect".
Changed description:
The server starts fine and clients can connect. After a port scan from the second computer, the clients are disconnected and can not reconnect.
00
repro:
01) run `bedrock_server.exe`
02) connect with Minecraft Win10 edition
03) run `nmap -sU -p 19132 -Pn server_ip` from another computer on the network
00
Expected Behavior: nothing should happen
0Actual Behavior: Client is disconnected and can not reconnect until the server is killed and restarted.
0
edit: This also works on realms. I created the trial realm and it ended up on 20.44.82.190:30223. Now when I try to connect, I just get "Unable to connect".
Changed description:
The server starts fine and clients can connect. After a port scan from the second computer, the clients are disconnected and can not reconnect.
00
repro:
01) run `bedrock_server.exe`
02) connect with Minecraft Win10 edition
03) run `nmap -sU -p 19132 -Pn server_ip` from another computer on the network
00
Expected Behavior: nothing should happen
0Actual Behavior: Client is disconnected and can not reconnect until the server is killed and restarted.
00
edit: This also works on realms. I created the trial realm and it ended up on 20.44.82.190:30223. Now when I try to connect, I just get "Unable to connect".
0
edit2: It came back up a couple of minutes later. When I killed my local instance, the executable didn't actually crash. I could still issue commands.
Changed description:
The server starts fine and clients can connect. After a port scan from the second computer, the clients are disconnected and can not reconnect.
00
repro:
01) run `bedrock_server.exe`
02) connect with Minecraft Win10 edition
03) run `nmap -sU -p 19132 -Pn server_ip` from another computer
0
Expected Behavior: nothing should happen
0Actual Behavior: Client is disconnected and can not reconnect until the server is killed and restarted.
00
edit: This also works on realms. I created the trial realm and it ended up on 20.44.82.190:30223. Now when I try to connect, I just get "Unable to connect".
00
edit2: It came back up a couple of minutes later. When I killed my local instance, the executable didn't actually crash. I could still issue commands.
0
Changed description:
The server starts fine and clients can connect. After a port scan from the second computer, the clients are disconnected and can not reconnect.
00
repro:
01) run `bedrock_server.exe`
02) connect with Minecraft Win10 edition
03) run `nmap -sU -p 19132 -Pn server_ip` from another computer
00
Expected Behavior: nothing should happen
0Actual Behavior: Client is disconnected and can not reconnect until the server is killed and restarted.
00
edit: This also works on realms. I created the trial realm and it ended up on 20.44.82.190:30223. Now when I try to connect, I just get "Unable to connect".
00
edit2: It came back up
Changed description:
The server starts fine and clients can connect. After a port scan from
0
repro:
01) run `bedrock_server.exe`
02) connect with Minecraft Win10 edition
03) run `nmap -sU -p 19132 -Pn server_ip` from another computer
00
Expected Behavior: nothing should happen
0Actual Behavior: Client is disconnected and can not reconnect until the server is killed and restarted.
00
edit: This also works on realms. I created the trial realm and it ended up on 20.44.82.190:30223. Now when I try to connect, I just get "Unable to connect".
00
edit2: It came back up on a different ip a couple of minutes later. When I killed my local instance, the executable didn't actually crash. I could still issue commands.
0
The server starts fine and clients can connect. After a port scan from
0
repro:
01) run `bedrock_server.exe`
02) connect with Minecraft Win10 edition
03) run `nmap -sU -p 19132 -Pn server_ip` from another computer
00
Expected Behavior: nothing should happen
0Actual Behavior: Client is disconnected and can not reconnect until the server is killed and restarted.
00
edit: This also works on realms. I created the trial realm and it ended up on 20.44.82.190:30223. Now when I try to connect, I just get "Unable to connect".
00
edit2: It came back up on a different ip a couple of minutes later. When I killed my local instance, the executable didn't actually crash. I could still issue commands.
0
Changed description:
The server starts fine and clients can connect. After a port scan from
0
repro:
01) run `bedrock_server.exe`
02) connect with Minecraft Win10 edition
03) run `nmap -sU -p 19132 -Pn server_ip` from another computer
00
Expected Behavior: nothing should happen
0Actual Behavior: Client is disconnected and can not reconnect until the server is killed and restarted.
00
edit: This also works on realms. I created the trial realm and it ended up on 20.44.82.190:30223. Now when I try to connect, I just get "Unable to connect".
00
edit2: It came back up on a different ip a couple of minutes later. When I killed my local instance, the executable didn't actually crash. I could still issue commands.
0
The server starts fine and clients can connect. After a port scan from
0
repro:
01) run `bedrock_server.exe`
02) connect with Minecraft Win10 edition
03) run `nmap -sU -p 19132 -Pn server_ip` from another computer
00
Expected Behavior: nothing should happen
0Actual Behavior: Client is disconnected and can not reconnect until the server is killed and restarted.
00
edit: This also works on realms. I created the trial realm and it ended up on 20.44.82.190:30223. Now when I try to connect, I just get "Unable to connect".
00
edit2: It came back up on a different ip a couple of minutes later. When I killed my local instance, the executable didn't actually crash. I could still issue commands.
Changed description:
The server starts fine and clients can connect. After a port scan from the second computer, the clients are disconnected and can not reconnect.
00
repro:
01) run `bedrock_server.exe`
02) connect with Minecraft Win10 edition
03) run `nmap -sU -p 19132 -Pn server_ip` from another computer
00
Expected Behavior: nothing should happen
0Actual Behavior: Client is disconnected and can not reconnect until the server is killed and restarted.
00
edit: This also works on realms. I created the trial realm and it ended up on 20.44.82.190:30223. Now when I try to connect, I just get "Unable to connect".
00
edit2: It came back up on a different ip a couple of minutes later. When I killed my local instance, the executable didn't actually crash. I could still issue commands.
The server starts fine and clients can connect. After a port scan from the second computer, the clients are disconnected and can not reconnect.
00
repro:
01) run `bedrock_server.exe`
02) connect with Minecraft Win10 edition
03) run `nmap -sU -p 19132 -Pn server_ip` from another computer
00
Expected Behavior: nothing should happen
0Actual Behavior: Client is disconnected and can not reconnect until the server is killed and restarted.
0
edit: This also works on realms. I created the trial realm and it ended up on 20.44.82.190:30223. Now when I try to connect, I just get "Unable to connect".
00
edit2: It came back up on a different ip a couple of minutes later. When I killed my local instance, the executable didn't actually crash. I could still issue commands.
0
Changed description:
The server starts fine and clients can connect. After a port scan from the second computer, the clients are disconnected and can not reconnect.
00
repro:
01) run `bedrock_server.exe`
02) connect with Minecraft Win10 edition
03) run `nmap -sU -p 19132 -Pn server_ip`
0
Expected Behavior: nothing should happen
0Actual Behavior: Client is disconnected and can not reconnect until the server is killed and restarted. One (and just one) of the threads started by the server exits with 0 immediately after receiving the ping.
00
edit: This also works on realms. I created the trial realm and it ended up on 20.44.82.190:30223. Now when I try to connect, I just get "Unable to connect".
00
edit2: It came back up on a different ip a couple of minutes later. When I killed my local instance, the executable didn't actually crash. I could still issue commands.
00
The server starts fine and clients can connect. After a port scan from the second computer, the clients are disconnected and can not reconnect.
00
repro:
01) run `bedrock_server.exe`
02) connect with Minecraft Win10 edition
03)
0
Expected Behavior: nothing should happen
0Actual Behavior: Client is disconnected and can not reconnect until the server is killed and restarted. One (and just one) of the threads started by the server exits with 0 immediately after receiving the ping.
00
edit: This also works on realms. I created the trial realm and it ended up on 20.44.82.190:30223. Now when I try to connect, I just get "Unable to connect".
00
edit2: It came back up on a different ip a couple of minutes later. When I killed my local instance, the executable didn't actually crash. I could still issue commands.
00
Changed description:
The server starts fine and clients can connect. After a port scan from the second computer, the clients are disconnected and can not reconnect.
00
repro:
01) run `bedrock_server.exe`
02) connect with Minecraft Win10 edition
03) from another network, run `nmap -sU -p 19132 -Pn server_ip`
00
Expected Behavior: nothing should happen
0Actual Behavior:
0
edit: This also works on realms. I created the trial realm and it ended up on 20.44.82.190:30223. Now when I try to connect, I just get "Unable to connect".
00
edit2: It came back up on a different ip a couple of minutes later. When I killed my local instance, the executable didn't actually crash. I could still issue commands.
00
The server starts fine and clients can connect. After a port scan from the second computer, the clients are disconnected and can not reconnect.
00
repro:
01) run `bedrock_server.exe`
02) connect with Minecraft Win10 edition
03) from another network, run `nmap -sU -p 19132 -Pn server_ip`
00
Expected Behavior: nothing should happen
0Actual Behavior: One (and just one) of the threads started by the server exits with 0 immediately after receiving the ping.
0
edit: This also works on realms. I created the trial realm and it ended up on 20.44.82.190:30223. Now when I try to connect, I just get "Unable to connect".
00
edit2: It came back up on a different ip a couple of minutes later. When I killed my local instance, the executable didn't actually crash. I could still issue commands.
00
Changed description:
The server starts fine and clients can connect. After a port scan from the second computer, the clients are disconnected and can not reconnect.
00
repro:
01) run `bedrock_server.exe`
02) connect with Minecraft Win10 edition
03) from another network, run `nmap -sU -p 19132 -Pn server_ip`
00
Expected Behavior: nothing should happen
0Actual Behavior: One (and just one) of the threads started by the server exits with 0 immediately after receiving the p
0
edit: This also works on realms. I created the trial realm and it ended up on 20.44.82.190:30223. Now when I try to connect, I just get "Unable to connect".
00
edit2: It came back up on a different ip a couple of minutes later. When I killed my local instance, the executable didn't actually crash. I could still issue commands.
00
The server starts fine and clients can connect. After a port scan from the second computer, the clients are disconnected and can not reconnect.
00
repro:
01) run `bedrock_server.exe`
02) connect with Minecraft Win10 edition
03) from another network, run `nmap -sU -p 19132 -Pn server_ip`
00
Expected Behavior: nothing should happen
0Actual Behavior: One (and just one) of the threads started by the server exits with 0 immediately after receiving the p
0
edit: This also works on realms. I created the trial realm and it ended up on 20.44.82.190:30223. Now when I try to connect, I just get "Unable to connect".
00
edit2: It came back up on a different ip a couple of minutes later. When I killed my local instance, the executable didn't actually crash. I could still issue commands.
00
Changed description:
The server starts fine and clients can connect. After a port scan from the second computer, the clients are disconnected and can not reconnect.
00
repro:
01) run `bedrock_server.exe`
02) connect with Minecraft Win10 edition
03) from another network, run `nmap -sU -p 19132 -Pn server_ip`
00
Expected Behavior: nothing should happen
0Actual Behavior: One (and just one) of the threads started by the server exits with 0 immediately after receiving the packet (or packets?) from the scan. Client is disconnected and can not reconnect until the server is killed and restarted.
00
edit: This also works on realms. I created the trial realm and it ended up on 20.44.82.190:30223.
0
edit2: It came back up on a different ip a couple of minutes later. When I killed my local instance, the executable didn't actually crash. I could still issue commands.
00
Removed Security Level: Minecraft - Private
Changed environment:
I could not find the version in the dropdown. The bedrock server reports itself as `1.12.1.1`
00
Windows 10, server downloaded from https://www.minecraft.net/en-us/download/server/bedrock/ and run with no changes
00
Minecraft Win10 edition 1.12.1
00
Second computer on the same network
Windows 10, BDS 1.12.1.1
Added Security Level: Minecraft - Private
Added is duplicated by link: BDS-3242Cannot join remote linux bedrock server from androidDuplicate
Added affects versions: 1.14.30
Added is duplicated by link: BDS-7843A bug can make the server inaccessible to playersDuplicate
Added is duplicated by link: BDS-3616[DoS attack] server crashed Duplicate
Added affects versions: 1.14.32.1
Added is duplicated by link: BDS-8309Custom net packet make BDS disconnectDuplicate
Added affects versions: 1.16.20
Resolution: Unresolved → Fixed
If this issue turns out to be legitimate and gets picked up, could you please add Jira user `competentcuttlefish` to the issue? He is the one who actually noticed this bug and would like to follow along. Thanks!
MEQS_KEEP_PRIVATE
Another instance of this issue has been reported under
BDS-7843.