Authenticated resolver crash via invalid memory access
Published Jul 19, 2021 · Updated Aug 4, 2024
Memory corruption in MikroTik RouterOS before 6.47 allows remote authenticated users to crash the resolver process with a crafted packet. The resolver handles the packet with an invalid memory access, producing signal 11 in the published 6.46.5 crash dump. Reachability requires authenticated access to the packet-handling interface; the demonstrated consequence is resolver service interruption, not code execution.
Summary
What happened
Memory corruption in MikroTik RouterOS before 6.47 allows remote authenticated users to crash the resolver process with a crafted packet. The resolver handles the packet with an invalid memory access, producing signal 11 in the published 6.46.5 crash dump. Reachability requires authenticated access to the packet-handling interface; the demonstrated consequence is resolver service interruption, not code execution.
The record
- CVE
- CVE-2020-20249
- Published
- Jul 19, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1499.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 19, 2021CVE 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.
Public exploit references
- RouterOS resolver crash proof of conceptproof of concept · 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