Authenticated btest process crash via reachable assertion
Published May 18, 2021 · Updated Aug 4, 2024
Reachable assertion in MikroTik RouterOS 6.44.6 allows remote authenticated users to crash the btest process via a crafted packet. The btest packet handler accepts attacker-controlled packet content that reaches an internal assertion, aborting /nova/bin/btest with signal 6. Valid RouterOS credentials and network access to the bandwidth-test service are required; exploitation interrupts btest rather than the entire device.
Summary
What happened
Reachable assertion in MikroTik RouterOS 6.44.6 allows remote authenticated users to crash the btest process via a crafted packet. The btest packet handler accepts attacker-controlled packet content that reaches an internal assertion, aborting /nova/bin/btest with signal 6. Valid RouterOS credentials and network access to the bandwidth-test service are required; exploitation interrupts btest rather than the entire device.
The record
- CVE
- CVE-2020-20214
- Published
- May 18, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-617, 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