Authenticated sniffer-process crash via invalid memory access
Published May 18, 2021 · Updated Aug 4, 2024
Memory corruption in MikroTik RouterOS 6.46.3 allows remote authenticated users to crash the sniffer process via a crafted packet. The /nova/bin/sniffer process performs an invalid memory access while handling the packet, terminating with SIGSEGV in published tests. Access to an authenticated RouterOS session is required, and the demonstrated consequence is interruption of packet-sniffing service rather than code execution.
Summary
What happened
Memory corruption in MikroTik RouterOS 6.46.3 allows remote authenticated users to crash the sniffer process via a crafted packet. The /nova/bin/sniffer process performs an invalid memory access while handling the packet, terminating with SIGSEGV in published tests. Access to an authenticated RouterOS session is required, and the demonstrated consequence is interruption of packet-sniffing service rather than code execution.
The record
- CVE
- CVE-2020-20236
- Published
- May 18, 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
- May 18, 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