CVERadar
MEDIUM · CVSS 3.1 5.4Public PoCEPSS 1.29% (p70)Threat level 31

CVE-2024-54772: CVE-2024-54772: An issue was discovered in the Winbox service of MikroTik RouterOS long-term release v6.43…

mikrotik · routeros · NVD published 2025-02-12 · posted 2025-02-11 · last modified 2026-06-17

What it is

An issue was discovered in the Winbox service of MikroTik RouterOS long-term release v6.43.13 through v6.49.13 and stable v6.43 through v7.17.2. A patch is available in the stable release v6.49.18. A discrepancy in response size between connection attempts made with a valid username and those with an invalid username allows attackers to enumerate for valid accounts.

WeaknessCWE-208
CVSS vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N (source: 134c704f-9b21-4f2e-91b3-4a467353bcc0)
ATT&CK tacticsn/a

Exploitation evidence

First exploit evidence seen: 2025-02-11 (earliest date across the sources below).

Exploited in the wild

No source on this site lists in-the-wild exploitation yet (CISA KEV, VulnCheck KEV).

Public exploit code

GitHub proof-of-concept repositories

2 public repositories from 2 accounts, first seen 2025-02-11. Most starred: deauther890/CVE-2024-54772 (35 stars), view repository.

Verify before running: public PoCs can be malicious. Read the code and only run it in an isolated lab. A PoC means exploit code is public, not that this CVE is exploited in the wild.

Sources: nomi-sec/PoC-in-GitHub.

How to fix it

Fixed versions

  • mikrotik routeros: upgrade to 6.49.18 or later (affected from 6.43)
  • mikrotik routeros: upgrade to 7.18 or later (affected from 7.1)

Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.

Vendor advisories and patches

No vendor-tagged reference yet; see the full reference list.

Detection Generic guidance

    Response checklist Generic guidance

    1. Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
    2. Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
    3. Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
    4. Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.

    Sources