Device reboot via unreleased SMB allocations
Published Feb 28, 2022 · Updated Aug 4, 2024
Resource exhaustion in MikroTik RouterOS 6.47 allows remote attackers to reboot devices through repeated crafted SMB requests. The SMB process fails to free malloc-backed memory after handling Session Setup Request packets, so requests with updated message identifiers progressively exhaust memory. No authentication is required, and successful exploitation reboots the device, interrupting its network services.
Summary
What happened
Resource exhaustion in MikroTik RouterOS 6.47 allows remote attackers to reboot devices through repeated crafted SMB requests. The SMB process fails to free malloc-backed memory after handling Session Setup Request packets, so requests with updated message identifiers progressively exhaust memory. No authentication is required, and successful exploitation reboots the device, interrupting its network services.
The record
- CVE
- CVE-2020-22844
- Published
- Feb 28, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 28, 2022CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- MikroTik RouterOS SMB memory-exhaustion proof of conceptfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo