MikroTik RouterOS
Improper restriction of excessive authentication attempts in MikroTik RouterOS and Cloud Hosted Router
Edge device · Router / network deviceknown edge product: MikroTik RouterOS Improper restriction of excessive authentication (high confidence)
MikroTik RouterOS contains a weakness in its API authentication handling that lacks effective safeguards against excessive login attempts. The system does not enforce meaningful rate-limiting, account lockout, or source-based restrictions, allowing repeated authentication failures to proceed without defensive response. In some versions, a fixed per-connection delay is present, but it can be bypassed through concurrent sessions, resulting in continued high-volume attempts. This deficiency increases the risk that an attacker could eventually obtain valid credentials and gain unauthorized access to administrative services.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- All versions
- All versions
Mitigation
The record names no fix. Check the vendor advisory below.
Workaround
No fix is currently available from MikroTik. Until a fix is available, MikroTik recommends that users adopt the following mitigations: Use a strong VPN or other additional protection layer if the API is exposed to public networks. * Configure the unsuccessful-attempt time range (0.1 to 0.5 seconds) in /ip service for all services, including the API, once available. * Connect initially from a trusted network (LAN) port only, then configure the router per your security requirements. * Restrict/limit access to management services from untrusted networks. * Apply firewall rules to control and restrict access to management services where possible. * Use long, randomly generated passwords rather than weak or default-simple ones, to keep the brute-force search space impractically large. * Keep the default randomly generated device password, or replace it with an equally strong one, since minimum complexity isn't enforced by default. Users are encouraged to reach out to MikroTik (https://mikrotik.com/support) for further support.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.