Authenticated bfd process crash via crafted packet
Published May 18, 2021 · Updated Aug 4, 2024
Memory corruption in MikroTik RouterOS before 6.47 allows remote authenticated users to crash the bfd process with a crafted packet. The bfd process mishandles the packet and performs an invalid memory access that dereferences a null pointer. Valid RouterOS credentials are required, and the demonstrated consequence is a crash of the bfd process rather than data disclosure or modification.
Summary
What happened
Memory corruption in MikroTik RouterOS before 6.47 allows remote authenticated users to crash the bfd process with a crafted packet. The bfd process mishandles the packet and performs an invalid memory access that dereferences a null pointer. Valid RouterOS credentials are required, and the demonstrated consequence is a crash of the bfd process rather than data disclosure or modification.
The record
- CVE
- CVE-2020-20220
- Published
- May 18, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-119, 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.
Weakness, pattern, technique
Public exploit references
- RouterOS bfd crafted-packet 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