MikroTik RouterOS up to 6.46 netwatch divide by zero

Summaryinfo

A vulnerability has been found in MikroTik RouterOS up to 6.46 and classified as problematic. This affects an unknown function of the file /ram/pckg/advanced-tools/nova/bin/netwatch. This manipulation causes divide by zero. This vulnerability is handled as CVE-2020-20264. The attack can be initiated remotely. Additionally, an exploit exists. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in MikroTik RouterOS up to 6.46 (Router Operating System). It has been declared as problematic. Affected by this vulnerability is an unknown part of the file /ram/pckg/advanced-tools/nova/bin/netwatch. The manipulation with an unknown input leads to a divide by zero vulnerability. The CWE definition for the vulnerability is CWE-369. The product divides a value by zero. As an impact it is known to affect availability.

The weakness was released 05/20/2021. The advisory is shared at seclists.org. This vulnerability is known as CVE-2020-20264. Technical details and also a public exploit are known. MITRE ATT&CK project uses the attack technique T1499 for this issue.

It is possible to download the exploit at github.com. It is declared as proof-of-concept.

Upgrading to version 6.47 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Router Operating System

Vendor

• MikroTik

Name

• RouterOS

Version

• 6.0
• 6.1
• 6.2
• 6.3
• 6.4
• 6.5
• 6.6
• 6.7
• 6.8
• 6.9
• 6.10
• 6.11
• 6.12
• 6.13
• 6.14
• 6.15
• 6.16
• 6.17
• 6.18
• 6.19
• 6.20
• 6.21
• 6.22
• 6.23
• 6.24
• 6.25
• 6.26
• 6.27
• 6.28
• 6.29
• 6.30
• 6.31
• 6.32
• 6.33
• 6.34
• 6.35
• 6.36
• 6.37
• 6.38
• 6.39
• 6.40
• 6.41
• 6.42
• 6.43
• 6.44
• 6.45
• 6.46

License

• commercial

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion