Authenticated traceroute crash via loop counter corruption
Published May 3, 2021 · Updated Aug 4, 2024
Memory corruption in MikroTik RouterOS 6.44.6 allows remote authenticated users to crash the traceroute process via a crafted packet. The /nova/bin/traceroute process mishandles its loop counter while processing the packet, causing an invalid memory access. Valid RouterOS credentials and network access are required, and the documented consequence is termination of traceroute rather than a full-device outage.
Summary
What happened
Memory corruption in MikroTik RouterOS 6.44.6 allows remote authenticated users to crash the traceroute process via a crafted packet. The /nova/bin/traceroute process mishandles its loop counter while processing the packet, causing an invalid memory access. Valid RouterOS credentials and network access are required, and the documented consequence is termination of traceroute rather than a full-device outage.
The record
- CVE
- CVE-2020-20218
- Published
- May 3, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1499
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 3, 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
No public exploit references are available in this record.
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