You will be prompted as to if you want to upgrade the firmware. To upgrade the firmware, run the following command: It should print out the version you are on, and if there is a upgraded version available. You can also upgrade the Firmware if needed.Ĭheck the firmware version, and determine if you need to upgrade. The router will download the updated RouterOS packages, install them, and proceed to automatically reboot. The following command will download and install the latest update. If you are on a version between (and including) v6.29 through to v6.42, you should upgrade to prevent someone from exploiting this vulnerability. Upgrade RouterOS to v6.42.1 or higherĬheck your current version, and check for a new version of RouterOS.Įxample output showing a new version available: Keep in mind all IP addresses that you may need to add, to prevent you locking yourself out of the router, as this can prevent access from the LAN side as well. This will add a filter rule at the very beginning on your firewall, blocking access to the WinBox service from any IP address not in the WinboxAccess address list created above. ip firewall filter add chain=input src-address-list=!WinboxAccess protocol=tcp dst-port=8291 action=drop place-before=0 Set up a firewall to block WinBox access from any addresses/networks that are not specified in the WinboxAccess address list. ip firewall address-list add list=WinboxAccess address="10.0.0.44/32"Īdd as many IP addresses/networks as needed to the address list. ip firewall address-list add list=WinboxAccess address="192.168.0.0/24" If you are using a version of RouterOS that has address-list functionality:Ĭreate an address list called WinboxAccess and assign IP addresses and networks to the list Restrict WinBox access using the IP firewall In this example, the 192.168.0.* network is allowed, as well as the individual 10.0.0.44 IP address. Once this has been set, only addresses in the specified list of addresses will be able to connect. You can use the following command to set up a number of allowed IP addresses/networks that can connect to the WinBox service. If the remote device that needs to connect has a static IP address that doesn’t change, you can set up a filter on the WinBox service itself, using an “Available From” list. Sometimes you may need to remotely manage a RouterOS device using WinBox. Restrict WinBox access using the “Available From” list If you manage your router using another method, such as SSH, and you don’t actually need WinBox access, you can simply disable the WinBox service. You may not need to do all of them to prevent this vulnerability, but the more locked down the router is, the better. Here are some options to prevent your RouterOS device from being exploited. However, there is a chance that this could be exploited from inside the LAN by a malicious user if your rules allow access on the LAN side.įor more information on the exploit, please read the forum post on the Mikrotik site:Īdvisory: Vulnerability exploiting the Winbox port This remote exploit relies on the WinBox service being accessible, so if you don’t have that enabled, or you are blocking it via a IP firewall rule, or are restricting users via the WinBox services ‘Available From’ list, you should be safe from this vulnerability effecting you. This will appear in the RouterOS logs, as a WinBox connection attempt that fails, and then a second attempt, which is successful. The remote user can then log in, and take control of the router. While it currently remains uncertain exactly how the exploit works, it would appear that a remote user can connect to the WinBox port (which is port 8291 by default), and download a user database file, without successfully authenticating. Version 6.42.1 for current (and v6.43rc4 for release candidate), has just been released, which has fixed this vulnerability, and should be upgraded to as soon as possible. This is currently effecting RouterOS versions v6.29 through to v6.42 in the current channel (and up to v6.43rc3 in the release candidate channel). It was discovered on the 23rd of April 2018, that there was a remote vulnerability being exploited in the wild, that is exploiting the Winbox service on RouterOS based devices (Mikrotik / Routerboard devices).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |