dbcve.org
RouterosOperating system · Mikrotik

CVE-2024-54772

MEDIUM · 5.4 CVSS v3.1 Published 2025-02-11
Fix available
A fix is available. Upgrade to 6.49.18 / 7.18 or later.
See remediation →
60/100
Remediation priority · Elevated
Public exploit Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
RouterosOperating system
Affected:>= 6.43, < 6.49.18>= 6.43.13, <= 6.49.13>= 7.1, < 7.18

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.49.18 / 7.18 or later
Fixed in 6.49.187.18
Recommended fix High confidence

RouterOS v6.49.18 or later for 6.x branch; RouterOS v7.18 or later for 7.x branch

  1. 1. Backup the current RouterOS configuration using the '/export' command or through Winbox/Files menu
  2. 2. Download the appropriate RouterOS upgrade package from MikroTik's download page (https://download.mikrotik.com/)
  3. 3. Upload the RouterOS .npk file to the router via Winbox > Files menu, or via FTP/SCP
  4. 4. Access the router via Winbox or SSH and reboot using the '/system reboot' command
  5. 5. After reboot, verify the new version with '/system resource print' and confirm the vulnerability is addressed
  6. 6. Verify all services are functioning normally and the configuration is intact
Caveat RouterOS upgrades are generally safe but always test in a lab environment first; some legacy packages or scripts may need adjustment after major version changes

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-54772 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-54772 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data