Authenticated service interruption via crafted SSH packet
Published Jul 19, 2021 · Updated Aug 4, 2024
Uncontrolled resource consumption in MikroTik RouterOS before 6.47 allows remote authenticated users to interrupt service via SSH. The sshd process consumes unbounded CPU and, on x86, memory while handling a crafted packet; the triggering packet fields are undisclosed. Valid RouterOS credentials and network access to SSH are required; affected devices become slow or unresponsive, and the demonstrated x86 system rebooted.
Summary
What happened
Uncontrolled resource consumption in MikroTik RouterOS before 6.47 allows remote authenticated users to interrupt service via SSH. The sshd process consumes unbounded CPU and, on x86, memory while handling a crafted packet; the triggering packet fields are undisclosed. Valid RouterOS credentials and network access to SSH are required; affected devices become slow or unresponsive, and the demonstrated x86 system rebooted.
The record
- CVE
- CVE-2020-20230
- Published
- Jul 19, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-400, 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.
Weakness, pattern, technique
Public exploit references
- CVE-2020-20230 proof-of-concept reportproof 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