Important security update

The SSH implementation is largely custom but it's not an implementation that is at fault but how it interacts with rest of RouterOS internals. The vulnerability is authentication bypass due to argument injection and IPC confusion. The direct cause is lack of sanitization of usernames being passed directly as arguments to another process.

Presence of ops user is indication of specific campaign but not necessity for exploit to function - any changes to configuration can be made, it's just that in this case attacker left themselves an easier backdoor for post-exploitation work.


Focus being on SSH is mostly due to it being most popular service being exposed, the actual vulnerability exists beyond that scope and affects every management service, though whether it can be exploited in same way is another question that needs investigation. You should however assume that they are all vulnerable.

For regular home device users and default configurations, the issue does not pose an immediate risk, but we still suggest all users to upgrade.

I do not agree with this statement. While "default configuration" part is true, the "regular home user" is a bit of a stretch here because it implicitly assumes that user did not go beyond QuickSet or the mentioned default configuration. Who's to say that "regular home user" did not expose WinBox port? It's really unnecessary to put it there and makes vulnerability seem less critical than it is.


Also I take big issue with the fact that MikroTik did not disclose that the vulnerability is being actively exploited. Note that patched versions explicitly check for existence of ops user with specific policies set, which confirms that MikroTik knew about this being exploited in the wild and tailored flagged checks for it specifically.

There are two most important questions you need to answer when publishing security bulletin - is it being actively exploited? What are immediate steps to take to remediate and what configuration is affected (or all)? In this case, the answers should've been clearly laid out:

  • Yes, this is under active exploitation
  • Any device with management port exposed to untrusted network is at risk

These two answers do not make it any easier for attacker to find a flaw (they can just diff .npk file and see that all management processes were updated) yet provide clear guidance and call for immediate action or remediation for your users. All this drama could've been easily avoided if you've just explained it clearly. Ironically, you did provide these answers, in unrelated replies on forums, but not in email, security bulletin or new version announcements.