v6.40.9 [bugfix] is released!

RouterOS version 6.40.9 has been released in public “bugfix” channel!

Before an upgrade:

  1. Remember to make backup/export files before an upgrade and save them on another storage device;
  2. Make sure the device will not lose power during upgrade process;
  3. Device has enough free storage space for all RouterOS packages to be downloaded.

What’s new in 6.40.9 (2018-Aug-20 07:46):

**MAJOR CHANGES IN v6.40.9:

!) security - fixed vulnerabilities CVE-2018-1156, CVE-2018-1157, CVE-2018-1158, CVE-2018-1159;
----------------------**

*) certificate - fixed “add-scep” template existence check when signing certificate;
*) defconf - fixed wAP LTE kit default configuration;
*) ethernet - improved large packet handling on ARM devices with wireless;
*) ethernet - removed obsolete slave flag from “/interface vlan” menu;
*) filesystem - fixed NAND memory going into read-only mode;
*) hotspot - fixed user authentication when queue from old session is not removed yet;
*) interface - fixed interface configuration responsiveness;
*) ipsec - fixed policies becoming invalid if added after a disabled policy;
*) ldp - properly load LDP configuration;
*) ppp - fixed “hunged up” grammar to “hung up” within PPP log messages;
*) sfp - hide “sfp-wavelength” parameter for RJ45 transceivers;
*) snmp - added remote CAP count OID for CAPsMAN;
*) supout - added “partitions” section to supout file;
*) tile - fixed Ethernet interfaces becoming unresponsive;
*) tr069-client - fixed unresponsive tr069 service when blackhole route is present;
*) userman - fixed compatibility with PayPal TLS 1.2;
*) userman - improved unique username generation process when adding batch of users;
*) winbox - added missing “dscp” and “clamp-tcp-mss” settings to IPv6 tunnels;
*) winbox - allow to specify full URL in SCEP certificate signing process;
*) winbox - by default specify keepalive timeout value for tunnel type interfaces;
*) winbox - show firmware upgrade message at the bottom of “System/RouterBOARD” menu;
*) winbox - show “scep-url” for certificates;
*) winbox - show “sector-writes” on ARM devices that have such counters;
*) winbox - show “sector-writes” on devices that have such counters;
*) winbox - show “System/Health” only on boards that have health monitoring;
*) wireless - added option to disable PMKID for WPA2;
*) wireless - enable all chains by default on devices without external antennas after configuration reset;
*) wireless - fixed packet processing after removing wireless interface from CAP settings;
*) wireless - improved client “channel-width” detection;
*) wireless - improved Nv2 PtMP performance;
*) wireless - increased stability on hAP ac^2 and cAP ac with legacy data rates;
*) wireless - updated “united-states” regulatory domain information;

To upgrade, click “Check for updates” at /system package in your RouterOS configuration interface, or head to our download page: http://www.mikrotik.com/download

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after some problem has appeared on device

Please keep this forum topic strictly related to this concrete RouterOS release.

Have been published the CVE?

Thanks you!

3011 and RB750 with MLPPPoE upgraded fine from 6.40.8

Webfig via SSL seems broken. After multiple logins session, the web server seems down and need to be restarted via disable and enable ip service www-ssl.

What is the point of publishing CVE numbers if the vulnerabilities are still private? Hackers can reverse engineer the changes in this version and figure out what the vulnerabilities are and start exploiting them, so there’s no point keeping it private once you publish the fix - it only benefits hackers since network admins can’t deploy mitigations if they don’t know what to mitigate!

I am with Rich on this one, it would be nice to know what these vulnerabilities are since you have patched them.
It is quite a big undertaking to upgrade all of our Mikrotiks as we have thousands of them and SLA’s that require we notify all our customers. Knowing what the vulnerabilities are would help us place a priority on upgrading them all.
Some of the recent exploits we were already protected from based on our network restrictions on the IP services, it would be nice to know if that is the case with these.


Edit: Looks like they are going to publish a blog post with more details soon per http://forum.mikrotik.com/t/v6-42-7-current-is-released/122533/49

!) security - fixed vulnerabilities CVE-2018-1156, CVE-2018-1157, CVE-2018-1158, CVE-2018-1159;

6.40.8 is vulnerable to this?

:frowning: Ah jeez , time to ring customers and tell them to brace for another set of sec patches.

Well at least the ansible script to autpatch everything will now come in handy I wrote a while ago.

yes, check 6.40.9 changelog (or 6.42.7) again, CVE was added afterwards, guess due to coordination? late addition?.

MAJOR CHANGES IN v6.40.9:

!) security - fixed vulnerabilities CVE-2018-1156, CVE-2018-1157, CVE-2018-1158, CVE-2018-1159;

Definitely knowing if best practices avoid the vulnerabilities beforehand would be great, or at least when will that post be published?

mind sharing? been meaning to start one, havent decided how i wanted to do it yet.

CVE details:
https://blog.mikrotik.com/security/security-issues-discovered-by-tenable.html

5 x 951G-2HnD updated without any problems … simple sonfiguration.
1 x 1100AHx4 - no problems with update
1 x 1100AHx4 - needed power cycle to start working after “Download&Instal”.

If your webserver on the Router is turned off… none of these CVEs are exploitable?
Also the word “authenticated” was used a bunch of times.

  1. Yes
  2. It means that a RouterOS username and password must be known. The user must log in. Then they can cause www server to crash. Basically this applies only to people with open Webfig interface for Read-only viewing, or such

This version is big catastrophe for me.
Upgraded more than 200 clients from 6.40.8 to 6.40.9 and client started disconnecting after couple seconds again and again.
I am not able to connect to them to made downgrade.
Newer devices (DiscLite) are more touched.
What do you recommend me?
Miroslav

When the clients are disconnecting, make a supout.rif file and email it to support. We will see what causes this. I don’t think there are any changes that could cause this, but we will see.

Thank you for the clarification!

Here is more info:

https://www.tenable.com/security/research/tra-2018-21

M.

We upgraded all our routers last night. Immediately lost the webserver on one, and today, they lost access to the webserver on another. A reboot brought access back up on them.
Scramble to log back in to all, and turn on SSH to make sure we have a way to get back in them. Looks like there may be a problem hiding in the firmware there?

Suggest that you have additional ways to get into the unit BEFORE you upgrade it.

Hi, great job always!

The fixed vulnerabilities only are involved with webfix at port 80 or also hotspot www service ?