Overview
Dnsmasq is vulnerable to a set of memory corruption issues handling DNSSEC data and a second set of issues validating DNS responses. These vulnerabilities could allow an attacker to corrupt memory on a vulnerable system and perform cache poisoning attacks against a vulnerable environment.
These vulnerabilities are also tracked as ICS-VU-668462 and referred to as DNSpooq.
Description
Dnsmasq is widely used open-source software that provides DNS forwarding and caching (and also a DHCP server). Dnsmasq is common in Internet-of-Things (IoT) and other embedded devices.
JSOF reported multiple memory corruption vulnerabilities in dnsmasq due to boundary checking errors in DNSSEC handling code.
- CVE-2020-25681: A heap-based buffer overflow in dnsmasq in the way it sorts RRSets before validating them with DNSSEC data in an unsolicited DNS response
- CVE-2020-25682: A buffer overflow vulnerability in the way dnsmasq extract names from DNS packets before validating them with DNSSEC data
- CVE-2020-25683: A heap-based buffer overflow in get_rdata subroutine of dnsmasq, when DNSSEC is enabled and before it validates the received DNS entries
- CVE-2020-25687: A heap-based buffer overflow in sort_rrset subroutine of dnsmasq, when DNSSEC is enabled and before it validates the received DNS entries
JSOF also reported vulnerabilities in DNS response validation that can result in DNS cache poisoning.
- CVE-2020-25684: Dnsmasq does not validate the combination of address/port and the query-id fields of DNS request when accepting DNS responses
- CVE-2020-25685: Dnsmasq uses a weak hashing algorithm (CRC32) when compiled without DNSSEC to validate DNS responses
- CVE-2020-25686: Dnsmasq does not check for an existing pending request for the same name and forwards a new request thus allowing an attacker to perform a "Birthday Attack" scenario to forge replies and potentially poison the DNS cache
Note: These cache poisoning scenarios and defenses are discussed in IETF RFC5452.
Impact
The memory corruption vulnerabilities can be triggered by a remote attacker using crafted DNS responses that can lead to denial of service, information exposure, and potentially remote code execution. The DNS response validation vulnerabilities allow an attacker to use unsolicited DNS responses to poison the DNS cache and redirect users to arbitrary sites.
Solution
Apply updates
These vulnerabilities are addressed in dnsmasq 2.83. Users of IoT and embedded devices that use dnsmasq should contact their vendors.
Follow security best-practices
Consider the following security best-practices to protect DNS infrastructure:
- Protect your DNS clients using stateful-inspection firewall that provide DNS security (e.g., stateful firewalls and NAT devices can block unsolicited DNS responses, DNS application layer inspection can prevent forwarding of anomalous DNS packets).
- Provide secure DNS recursion service with features such as DNSSEC validation and the interim 0x20-bit encoding as part of enterprise DNS services where applicable.
- Prevent exposure of IoT devices and lightweight devices directly over the Internet to minimize abuse of DNS.
- Implement a Secure By Default configuration suitable for your operating environment (e.g., disable caching on embedded IoT devices when an upstream caching resolver is available).
Acknowledgements
Moshe Kol and Shlomi Oberman of JSOF researched and reported these vulnerabilities. Simon Kelley (author of dnsmasq) worked closely with collaborative vendors (Cisco, Google, Pi-Hole, Redhat) to develop patches to address these security vulnerabilities. GitHub also supported these collaboration efforts providing support to use their GitHub Security Advisory platform for collaboration.
This document was written by Vijay Sarvepalli.
Vendor Information
Arista Networks Affected
Statement Date: January 04, 2021
| CVE-2020-25681 | Not Affected |
| CVE-2020-25682 | Not Affected |
| CVE-2020-25683 | Not Affected |
| CVE-2020-25684 | Affected |
| CVE-2020-25685 | Affected |
| CVE-2020-25686 | Affected |
| CVE-2020-25687 | Not Affected |
Vendor Statement
We have not received a statement from the vendor.
Check Point Affected
Statement Date: February 08, 2021
| CVE-2020-25681 | Not Affected |
| CVE-2020-25682 | Not Affected |
| CVE-2020-25683 | Not Affected |
| CVE-2020-25684 | Affected |
| CVE-2020-25685 | Affected |
| CVE-2020-25686 | Affected |
| CVE-2020-25687 | Not Affected |
Vendor Statement
Check Point Gaia is not vulnerable.
Check Point SMB is vulnerable to CVE-2020-25686, CVE-2020-25684, CVE-2020-25685 on internal (LAN, Wi-Fi) networks. And updated firware is available at https://supportcenter.checkpoint.com/
Cisco Affected
Statement Date: January 02, 2021
| CVE-2020-25681 | Not Affected |
| CVE-2020-25682 | Not Affected |
| CVE-2020-25683 | Not Affected |
| CVE-2020-25684 | Affected |
| CVE-2020-25685 | Affected |
| CVE-2020-25686 | Affected |
| CVE-2020-25687 | Not Affected |
Vendor Statement
We have not received a statement from the vendor.
References
Cradlepoint Affected
Statement Date: January 19, 2021
| CVE-2020-25681 | Affected |
| CVE-2020-25682 | Affected |
| CVE-2020-25683 | Affected |
| CVE-2020-25684 | Affected |
| CVE-2020-25685 | Affected |
| CVE-2020-25686 | Affected |
| CVE-2020-25687 | Affected |
Vendor Statement
Cradlepoint devices running NetCloud OS (NCOS) use dnsmasq for domain resolution, domain caching and DHCP services on the local LAN. DNS is a configurable service within NCOS therefore possible configuration states and potential impacts are listed.
Affected Components: NCOS versions up to 7.21.20
Recommendations:
Promptly test and upgrade to the latest NCOS version upon release
Disable (do not enable) DNSSEC until patched
Authenticate clients to the LAN using 802.1X
Do not configure firewall to expose DNS services (UDP port 53) on WAN interfaces
Default Configuration: DNSSEC disabled
Cradlepoint Severity: Low/Medium (dependent upon environment)
Potentially Impacted: Local LAN users, clients and services
Potential attack path: Local LAN
Associated CVEs: CVE-2020-25684, CVE-2020-25685, CVE-2020-25686
Modified Configuration: DNSSEC enabled
Cradlepoint Severity: Medium/High (dependent upon environment)
Potentially Impacted: Device and sub-services; Local LAN users, clients and services
Potential attack path: Local LAN
Associated CVEs: CVE-2020-25681, CVE-2020-25682, CVE-2020-25683, CVE-2020-25687
Modified Configuration: DNS services exposed on WAN
Cradlepoint Severity: Critical (dependent upon environment)
Potentially Impacted: See above
Potential attack paths:
WAN interfaces; Local LAN
Associated CVEs: See above
References
dd-wrt Affected
Statement Date: January 11, 2021
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Affected |
| CVE-2020-25685 | Affected |
| CVE-2020-25686 | Affected |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Digi International Affected
Statement Date: July 20, 2021
| CVE-2020-25681 | Affected |
| CVE-2020-25682 | Affected |
| CVE-2020-25683 | Affected |
| CVE-2020-25684 | Affected |
| CVE-2020-25685 | Affected |
| CVE-2020-25686 | Affected |
| CVE-2020-25687 | Affected |
Vendor Statement
Digi International has patched this in firmware versions 21.2.X.X on all of our DAL based products, which includes: Digi AnywhereUSB Plus 2 Digi AnywhereUSB Plus 8 Digi AnywhereUSB Plus 8 WiFi Digi AnywhereUSB Plus 24 Digi AnywhereUSB Plus 24 WiFi Digi Connect EZ1 (mini) Digi Connect EZ2 Digi Connect EZ4 Digi ConnectIT4 Digi ConnectIT16 Digi ConnectIT48 Digi ConnectIT-Mini Digi EX15 Digi EX15-PR Digi EX15W Digi EX15W-PR Digi EX12 Digi EX12-PR Digi IX10 Digi IX14 Digi IX15 Digi IX20
Digi IX20-PR Digi IX20W Digi IX20W-PR Digi LR54 Digi LR54W Digi TX54-Dual-Cellular Digi TX54-Dual-Cellular-PR Digi TX54-Dual-Wi-Fi Digi TX54-Single-Cellular Digi TX54-Single-Cellular-PR Digi TX64 Digi TX64-PR Digi TX64-Rail-Single-Cellular-PR Digi VirtualDAL Digi VirtualDAL-PR AcceleratedConcepts 6350-SR AcceleratedConcepts 6355-SR AcceleratedConcepts 6330-MX AcceleratedConcepts 6335-MX AcceleratedConcepts 6310-DX AcceleratedConcepts 5400-RM AcceleratedConcepts 5401-RM AcceleratedConcepts 6300-CX
References
Fujitsu Europe Affected
Statement Date: May 31, 2021
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Affected |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Affected |
| CVE-2020-25687 | Unknown |
Vendor Statement
Fujitsu is aware of the security vulnerabilities in software dnsmasq, also known as "DNSpooq".
Affected products are Fujitsu INTELLIEDGE, Fujitsu ServerView Services for ISM, Fujitsu SOA SysRollout Service, Fujitsu SOA Profile Management Service, Fujitsu ISM (Core) and Fujitsu FlexFrame Orchestrator (SAP). Updates are pending or already available.
The Fujitsu PSIRT has updated the state for Fujitsu PSIRT-IS-2021-011900 on https://security.ts.fujitsu.com (Security Notices) accordingly.
In case of questions regarding this Fujitsu PSIRT Security Notice, please contact the Fujitsu PSIRT (Fujitsu-PSIRT@ts.fujitsu.com).
Juniper Networks Affected
Statement Date: February 04, 2021
| CVE-2020-25681 | Not Affected |
| CVE-2020-25682 | Not Affected |
| CVE-2020-25683 | Not Affected |
| CVE-2020-25684 | Affected |
| CVE-2020-25685 | Affected |
| CVE-2020-25686 | Affected |
| CVE-2020-25687 | Not Affected |
Vendor Statement
The Juniper SIRT has investigated the impact of these vulnerabilities on Juniper products. Juniper Networks Junos OS, Space, and Contrail products are unaffected by these vulnerabilities.
Juniper Mist Access Points (APs) ship with Dnsmasq and are only affected by the vulnerabilities via DNS (CVE-2020-25684, CVE-2020-25685, CVE-2020-25686) 4.0/CVSS:3.1.
The Wi-Fi mPIM (Mini-PIM) card for SRX branch devices ship with Dnsmasq enabled by default and is reachable from the network. Only vulnerabilities (CVE-2020-25684, CVE-2020-25685, CVE-2020-25686): 4.0/CVSS:3.1 via DNS affect this card.
Code fixes are underway for Mist and the Mini-PIM card and customers should upgrade when those fixes are available.
Security Incident Response Team Juniper Networks
NetBSD Affected
Statement Date: June 19, 2023
| CVE-2020-25681 | Not Affected |
| CVE-2020-25682 | Not Affected |
| CVE-2020-25683 | Affected |
| CVE-2020-25684 | Not Affected |
| CVE-2020-25685 | Affected |
| CVE-2020-25686 | Not Affected |
| CVE-2020-25687 | Not Affected |
Vendor Statement
NetBSD does not ship dnsmasq and is not affected.
pkgsrc users, on any platform, who have elected to install net/dnsmasq may be affected, and were informed back in 2020 through the pkg-vulnerabilities database.
NETGEAR Affected
Statement Date: January 14, 2021
| CVE-2020-25681 | Affected |
| CVE-2020-25682 | Affected |
| CVE-2020-25683 | Affected |
| CVE-2020-25684 | Affected |
| CVE-2020-25685 | Affected |
| CVE-2020-25686 | Affected |
| CVE-2020-25687 | Affected |
Vendor Statement
Netgear has released fixes for multiple Dnsmasq security vulnerabilities on the following product affected models: RAX40 running firmware versions prior to v1.0.3.88 RAX35 running firmware versions prior to v1.0.3.88
NETGEAR strongly recommends that you download the latest firmware as soon as possible.
You and follow the steps mentioned in the security advisory to upgrade it to the latest version. https://kb.netgear.com/000062628/Security-Advisory-for-Multiple-Dnsmasq-Vulnerabilities-on-Some-Routers-PSV-2020-0463
Thanks, Rachit Dogra
References
OpenWRT Affected
Statement Date: January 19, 2021
| CVE-2020-25681 | Affected |
| Vendor Statement: | |
| Only package dnsmasq-full, which is not installed by default, is affected. | |
| CVE-2020-25682 | Affected |
| Vendor Statement: | |
| Only package dnsmasq-full, which is not installed by default, is affected. | |
| CVE-2020-25683 | Affected |
| Vendor Statement: | |
| Only package dnsmasq-full, which is not installed by default, is affected. | |
| CVE-2020-25684 | Affected |
| CVE-2020-25685 | Affected |
| Vendor Statement: | |
| Only package dnsmasq-full, which is not installed by default, is affected. | |
| CVE-2020-25686 | Affected |
| CVE-2020-25687 | Affected |
| Vendor Statement: | |
| Only package dnsmasq-full, which is not installed by default, is affected. | |
Vendor Statement
OpenWrt shipps the following variants: * dnsmasq * dnsmasq-dhcpv6 * dnsmasq-full
Only dnsmasq-full has support for DNSSEC and only this variant is affected by the problems in the DNSSEC code as far as we understand them. The other problems affect all variants. The default installation contains the dnsmasq package only, but the user can install the other variants.
References
Pi-Hole Affected
Statement Date: January 11, 2021
| CVE-2020-25681 | Affected |
| CVE-2020-25682 | Affected |
| CVE-2020-25683 | Affected |
| CVE-2020-25684 | Affected |
| CVE-2020-25685 | Affected |
| CVE-2020-25686 | Affected |
| CVE-2020-25687 | Affected |
Vendor Statement
We have not received a statement from the vendor.
Red Hat Affected
Statement Date: January 15, 2021
| CVE-2020-25681 | Affected |
| Vendor Statement: | |
| This issue affects the versions of dnsmasq as shipped with Red Hat Enterprise Linux 8, but it does not affect the versions of dnsmasq as shipped with Red Hat Enterprise Linux 5, 6, and 7 because they are not compiled with DNSSEC support. | |
| References: | |
| CVE-2020-25682 | Affected |
| Vendor Statement: | |
| This issue affects the versions of dnsmasq as shipped with Red Hat Enterprise Linux 8, but it does not affect the versions of dnsmasq as shipped with Red Hat Enterprise Linux 5, 6, and 7 because they are not compiled with DNSSEC support. | |
| References: | |
| CVE-2020-25683 | Affected |
| Vendor Statement: | |
| This issue affects the versions of dnsmasq as shipped with Red Hat Enterprise Linux 8, but it does not affect the versions of dnsmasq as shipped with Red Hat Enterprise Linux 5, 6, and 7 because they are not compiled with DNSSEC support. | |
| References: | |
| CVE-2020-25684 | Affected |
| Vendor Statement: | |
| This issue affects the versions of dnsmasq as shipped with Red Hat Enterprise Linux 5, 6, 7, and 8. Red Hat OpenStack Platform (RHOSP) and Red Hat Virtualization (RHV) are indirectly affected as well. | |
| References: | |
| CVE-2020-25685 | Affected |
| Vendor Statement: | |
| This issue affects the versions of dnsmasq as shipped with Red Hat Enterprise Linux 5, 6, 7, and 8. Red Hat Enterprise Linux 8 provides dnsmasq compiled with DNSSEC support, thus SHA-1 is used as a hash for query names instead of CRC32, making collisions harder to find. Red Hat OpenStack Platform (RHOSP) and Red Hat Virtualization (RHV) are indirectly affected as well. | |
| References: | |
| CVE-2020-25686 | Affected |
| Vendor Statement: | |
| This issue affects the versions of dnsmasq as shipped with Red Hat Enterprise Linux 5, 6, 7, and 8. Red Hat OpenStack Platform (RHOSP) and Red Hat Virtualization (RHV) are indirectly affected as well. | |
| References: | |
| CVE-2020-25687 | Affected |
| Vendor Statement: | |
| This issue affects the versions of dnsmasq as shipped with Red Hat Enterprise Linux 8, but it does not affect the versions of dnsmasq as shipped with Red Hat Enterprise Linux 5, 6, and 7 because they are not compiled with DNSSEC support. | |
| References: | |
References
Siemens Affected
Statement Date: January 19, 2021
| CVE-2020-25681 | Not Affected |
| CVE-2020-25682 | Not Affected |
| CVE-2020-25683 | Not Affected |
| CVE-2020-25684 | Affected |
| CVE-2020-25685 | Affected |
| CVE-2020-25686 | Affected |
| CVE-2020-25687 | Not Affected |
Vendor Statement
Siemens is aware of the security vulnerabilities in the Open Source component DNSmasq, as disclosed on 2021-01-19 and also known as "DNSpooq".
The impact to Siemens products is described in the Security Advisory SSA-646763, published on the Siemens ProductCERT page (https://www.siemens.com/cert/advisories).
In case of questions regarding this Security Advisory, please contact Siemens ProductCERT (productcert@siemens.com).
References
Sierra Wireless Affected
Statement Date: January 20, 2021
| CVE-2020-25681 | Affected |
| CVE-2020-25682 | Affected |
| CVE-2020-25683 | Affected |
| CVE-2020-25684 | Affected |
| CVE-2020-25685 | Affected |
| CVE-2020-25686 | Affected |
| CVE-2020-25687 | Affected |
Vendor Statement
Sierra Wireless products are affected by some of these vulnerabilities. Please check the security bulletin linked in the reference section for details on your product. Sierra Wireless would like to thank JSOF for discovering and responsibly reporting these issues, as well as the efforts of CERT/CC for coordinating the response.
References
Sophos Affected
Statement Date: January 20, 2021
| CVE-2020-25681 | Not Affected |
| References: | |
| CVE-2020-25682 | Not Affected |
| References: | |
| CVE-2020-25683 | Not Affected |
| References: | |
| CVE-2020-25684 | Affected |
| References: | |
| CVE-2020-25685 | Affected |
| References: | |
| CVE-2020-25686 | Affected |
| References: | |
| CVE-2020-25687 | Not Affected |
| References: | |
Vendor Statement
Sophos Red devices are impacted. More information to follow
References
SUSE Linux Affected
Statement Date: January 14, 2021
| CVE-2020-25681 | Affected |
| CVE-2020-25682 | Affected |
| CVE-2020-25683 | Affected |
| CVE-2020-25684 | Affected |
| CVE-2020-25685 | Affected |
| CVE-2020-25686 | Affected |
| CVE-2020-25687 | Affected |
Vendor Statement
We have not received a statement from the vendor.
Synology Affected
Statement Date: January 21, 2021
| CVE-2020-25681 | Not Affected |
| CVE-2020-25682 | Not Affected |
| CVE-2020-25683 | Not Affected |
| CVE-2020-25684 | Affected |
| CVE-2020-25685 | Affected |
| CVE-2020-25686 | Affected |
| CVE-2020-25687 | Not Affected |
Vendor Statement
We have not received a statement from the vendor.
References
Technicolor Affected
Statement Date: September 29, 2020
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Affected |
| Vendor Statement: | |
| we confirm that dnsmaq is affected by this vulnerability. however it is very unlikely to see real world exploitation of this vulnerability. It requires dnsmasq to be configured to do DNS requests to a rogue DNS that will serve these unrelated CNAME records. Devices are configured to request ISPs DNS. Moreover, these unrelated CNAME records are not valid and cannot be configured in a regular zone file; they require custom DNS server to be served. So, if you control a custom DNS and you can configure dnsmasq to request this DNS, no need to exploit a vulnerability to poison the cache, just answer what you want. Risk level : LOW CVSS v2 : 3.6 | |
| References: | |
| CVE-2020-25683 | Not Affected |
| Vendor Statement: | |
| DNSSEC is not available on dnsmasq version we use | |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Wind River Affected
Statement Date: October 14, 2020
| CVE-2020-25681 | Affected |
| CVE-2020-25682 | Affected |
| CVE-2020-25683 | Affected |
| CVE-2020-25684 | Affected |
| CVE-2020-25685 | Affected |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Zephyr Project Affected
Statement Date: October 27, 2020
| CVE-2020-25681 | Affected |
| CVE-2020-25682 | Affected |
| CVE-2020-25683 | Affected |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Affected |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
The Zephyr project consists of a core RTOS, numerous additional modules, and an extensive suite of test builds and test cases. This vulnerability does not directly affect the RTOS, or the additional modules. However, some of the test cases use the dnsmasq tool, which could render these testing environment vulnerable. In these test cases, the dnsmasq tool is used strictly by RTOS+test code running within the QEMU simulation environment. Attacks on dnsmasq could result in test failures causing a denial of service to the project (due to incorrect failures).
A10 Networks Not Affected
Statement Date: June 23, 2021
| CVE-2020-25681 | Not Affected |
| CVE-2020-25682 | Not Affected |
| CVE-2020-25683 | Not Affected |
| CVE-2020-25684 | Not Affected |
| CVE-2020-25685 | Not Affected |
| CVE-2020-25686 | Not Affected |
| CVE-2020-25687 | Not Affected |
Vendor Statement
Dnsmasq is not used in current and supported A10 Networks, Inc products.
Actiontec Not Affected
Statement Date: January 19, 2021
| CVE-2020-25681 | Not Affected |
| CVE-2020-25682 | Not Affected |
| CVE-2020-25683 | Not Affected |
| CVE-2020-25684 | Not Affected |
| CVE-2020-25685 | Not Affected |
| CVE-2020-25686 | Not Affected |
| CVE-2020-25687 | Not Affected |
Vendor Statement
we do not use dnsmasq in our products
Afero Not Affected
Statement Date: November 02, 2020
| CVE-2020-25681 | Not Affected |
| CVE-2020-25682 | Not Affected |
| CVE-2020-25683 | Not Affected |
| CVE-2020-25684 | Not Affected |
| CVE-2020-25685 | Not Affected |
| CVE-2020-25686 | Not Affected |
| CVE-2020-25687 | Not Affected |
Vendor Statement
We have not received a statement from the vendor.
Android Open Source Project Not Affected
Statement Date: November 23, 2020
| CVE-2020-25681 | Not Affected |
| CVE-2020-25682 | Not Affected |
| CVE-2020-25683 | Not Affected |
| CVE-2020-25684 | Not Affected |
| CVE-2020-25685 | Not Affected |
| CVE-2020-25686 | Not Affected |
| CVE-2020-25687 | Not Affected |
Vendor Statement
While Android does have Dnsmasq code but it is used in a limited capacity and cannot be attacked or exploited in the manner described in this report.
AVM GmbH Not Affected
Statement Date: October 30, 2020
| CVE-2020-25681 | Not Affected |
| CVE-2020-25682 | Not Affected |
| CVE-2020-25683 | Not Affected |
| CVE-2020-25684 | Not Affected |
| CVE-2020-25685 | Not Affected |
| CVE-2020-25686 | Not Affected |
| Vendor Statement: | |
| AVM does not use dnsmasq | |
| CVE-2020-25687 | Not Affected |
| Vendor Statement: | |
| AVM does not use dnsmasq | |
Vendor Statement
AVM doesn't use the dnsmasq project within its firmwares.
Barracuda Networks Not Affected
Statement Date: January 19, 2021
| CVE-2020-25681 | Not Affected |
| CVE-2020-25682 | Not Affected |
| CVE-2020-25683 | Not Affected |
| CVE-2020-25684 | Not Affected |
| CVE-2020-25685 | Not Affected |
| CVE-2020-25686 | Not Affected |
| CVE-2020-25687 | Not Affected |
Vendor Statement
We have not received a statement from the vendor.
Blackberry QNX Not Affected
Statement Date: October 30, 2020
| CVE-2020-25681 | Not Affected |
| CVE-2020-25682 | Not Affected |
| CVE-2020-25683 | Not Affected |
| CVE-2020-25684 | Not Affected |
| CVE-2020-25685 | Not Affected |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Not Affected |
Vendor Statement
We have not received a statement from the vendor.
Brocade Communication Systems Not Affected
Statement Date: November 25, 2020
| CVE-2020-25681 | Not Affected |
| CVE-2020-25682 | Not Affected |
| CVE-2020-25683 | Not Affected |
| CVE-2020-25684 | Not Affected |
| CVE-2020-25685 | Not Affected |
| CVE-2020-25686 | Not Affected |
| CVE-2020-25687 | Not Affected |
Vendor Statement
No Brocade Fibre Channel Products from Broadcom are currently known to be affected by these vulnerabilities.
eCosCentric Not Affected
Statement Date: November 25, 2020
| CVE-2020-25681 | Not Affected |
| CVE-2020-25682 | Not Affected |
| CVE-2020-25683 | Not Affected |
| CVE-2020-25684 | Not Affected |
| CVE-2020-25685 | Not Affected |
| CVE-2020-25686 | Not Affected |
| CVE-2020-25687 | Not Affected |
Vendor Statement
Do not use/supply Dnsmasq
eero Not Affected
Statement Date: January 15, 2021
| CVE-2020-25681 | Not Affected |
| CVE-2020-25682 | Not Affected |
| CVE-2020-25683 | Not Affected |
| CVE-2020-25684 | Not Affected |
| CVE-2020-25685 | Not Affected |
| CVE-2020-25686 | Not Affected |
| CVE-2020-25687 | Not Affected |
Vendor Statement
eero products do not use the affected functionality of the affected software products, and so are unaffected by these vulnerabilities.
Espressif Systems Not Affected
Statement Date: January 20, 2021
| CVE-2020-25681 | Not Affected |
| CVE-2020-25682 | Not Affected |
| CVE-2020-25683 | Not Affected |
| CVE-2020-25684 | Not Affected |
| CVE-2020-25685 | Not Affected |
| CVE-2020-25686 | Not Affected |
| CVE-2020-25687 | Not Affected |
Vendor Statement
Espressif doesn't use dnsmasq in any product SDKs or other published software, so is not affected.
F5 Networks Not Affected
Statement Date: December 05, 2020
| CVE-2020-25681 | Not Affected |
| Vendor Statement: | |
| The package dnsmasq and/or associated binaries are not installed on F5 products, therefore they are not affected by these vulnerabilities. | |
| CVE-2020-25682 | Not Affected |
| Vendor Statement: | |
| The package dnsmasq and/or associated binaries are not installed on F5 products, therefore they are not affected by these vulnerabilities. | |
| CVE-2020-25683 | Not Affected |
| Vendor Statement: | |
| The package dnsmasq and/or associated binaries are not installed on F5 products, therefore they are not affected by these vulnerabilities. | |
| CVE-2020-25684 | Not Affected |
| Vendor Statement: | |
| The package dnsmasq and/or associated binaries are not installed on F5 products, therefore they are not affected by these vulnerabilities. | |
| CVE-2020-25685 | Not Affected |
| Vendor Statement: | |
| The package dnsmasq and/or associated binaries are not installed on F5 products, therefore they are not affected by these vulnerabilities. | |
| CVE-2020-25686 | Not Affected |
| Vendor Statement: | |
| The package dnsmasq and/or associated binaries are not installed on F5 products, therefore they are not affected by these vulnerabilities. | |
| CVE-2020-25687 | Not Affected |
| Vendor Statement: | |
| The package dnsmasq and/or associated binaries are not installed on F5 products, therefore they are not affected by these vulnerabilities. | |
Vendor Statement
The package dnsmasq and/or associated binaries are not installed on F5 products, therefore they are not affected by these vulnerabilities.
FreeBSD Not Affected
Statement Date: September 24, 2020
| CVE-2020-25681 | Not Affected |
| CVE-2020-25682 | Not Affected |
| CVE-2020-25683 | Not Affected |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Not Affected |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
FreeBSD does not ship with dnsmasq as part of the base system. dnsmasq is available as part of the FreeBSD ports/pkg system, but the responsibility for analysis of risk lies with the administrator that chooses to install and configure dnsmasq.
F-Secure Corporation Not Affected
Statement Date: June 24, 2021
| CVE-2020-25681 | Not Affected |
| CVE-2020-25682 | Not Affected |
| CVE-2020-25683 | Not Affected |
| CVE-2020-25684 | Not Affected |
| CVE-2020-25685 | Not Affected |
| CVE-2020-25686 | Not Affected |
| CVE-2020-25687 | Not Affected |
Vendor Statement
Not Affected.
Google Not Affected
Statement Date: December 07, 2020
| CVE-2020-25681 | Not Affected |
| CVE-2020-25682 | Not Affected |
| CVE-2020-25683 | Not Affected |
| CVE-2020-25684 | Not Affected |
| CVE-2020-25685 | Not Affected |
| CVE-2020-25686 | Not Affected |
| CVE-2020-25687 | Not Affected |
Vendor Statement
We have not received a statement from the vendor.
HCC Embedded Not Affected
Statement Date: November 26, 2020
| CVE-2020-25681 | Not Affected |
| CVE-2020-25682 | Not Affected |
| CVE-2020-25683 | Not Affected |
| CVE-2020-25684 | Not Affected |
| CVE-2020-25685 | Not Affected |
| CVE-2020-25686 | Not Affected |
| CVE-2020-25687 | Not Affected |
Vendor Statement
We have not received a statement from the vendor.
Infoblox Not Affected
Statement Date: October 16, 2020
| CVE-2020-25681 | Not Affected |
| CVE-2020-25682 | Not Affected |
| CVE-2020-25683 | Not Affected |
| CVE-2020-25684 | Not Affected |
| CVE-2020-25685 | Not Affected |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Intel Not Affected
Statement Date: January 19, 2021
| CVE-2020-25681 | Not Affected |
| CVE-2020-25682 | Not Affected |
| CVE-2020-25683 | Not Affected |
| CVE-2020-25684 | Not Affected |
| CVE-2020-25685 | Not Affected |
| CVE-2020-25686 | Not Affected |
| CVE-2020-25687 | Not Affected |
Vendor Statement
We have not received a statement from the vendor.
LANCOM Systems GmbH Not Affected
Statement Date: January 14, 2021
| CVE-2020-25681 | Not Affected |
| CVE-2020-25682 | Not Affected |
| CVE-2020-25683 | Not Affected |
| CVE-2020-25684 | Not Affected |
| CVE-2020-25685 | Not Affected |
| CVE-2020-25686 | Not Affected |
| CVE-2020-25687 | Not Affected |
Vendor Statement
LANCOM Systems products are not affected by these vulnerabilities.
lwIP Not Affected
Statement Date: December 04, 2020
| CVE-2020-25681 | Not Affected |
| CVE-2020-25682 | Not Affected |
| CVE-2020-25683 | Not Affected |
| CVE-2020-25684 | Not Affected |
| CVE-2020-25685 | Not Affected |
| CVE-2020-25686 | Not Affected |
| CVE-2020-25687 | Not Affected |
Vendor Statement
lwIP does not use dnsmasq code. We've had similar bugs like 1 and 2 here in the past (with their own CVE), but these have been fixed quite a while ago.
Mbed TLS Not Affected
Statement Date: September 24, 2020
| CVE-2020-25681 | Not Affected |
| CVE-2020-25682 | Not Affected |
| CVE-2020-25683 | Not Affected |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Not Affected |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
McAfee Not Affected
Statement Date: May 17, 2021
| CVE-2020-25681 | Not Affected |
| CVE-2020-25682 | Not Affected |
| CVE-2020-25683 | Not Affected |
| CVE-2020-25684 | Not Affected |
| CVE-2020-25685 | Not Affected |
| CVE-2020-25686 | Not Affected |
| CVE-2020-25687 | Not Affected |
Vendor Statement
We have not received a statement from the vendor.
MikroTik Not Affected
Statement Date: September 29, 2020
| CVE-2020-25681 | Not Affected |
| Vendor Statement: | |
| Dnsmasq not used in MikroTik software | |
| CVE-2020-25682 | Not Affected |
| Vendor Statement: | |
| Dnsmasq not used in MikroTik software | |
| CVE-2020-25683 | Not Affected |
| Vendor Statement: | |
| Dnsmasq not used in MikroTik software | |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Not Affected |
| Vendor Statement: | |
| Dnsmasq not used in MikroTik software | |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
Dnsmasq not used in MikroTik software
Miredo Not Affected
Statement Date: January 19, 2021
| CVE-2020-25681 | Not Affected |
| CVE-2020-25682 | Not Affected |
| CVE-2020-25683 | Not Affected |
| CVE-2020-25684 | Not Affected |
| CVE-2020-25685 | Not Affected |
| CVE-2020-25686 | Not Affected |
| CVE-2020-25687 | Not Affected |
Vendor Statement
dnsmasq is not used.
netsnmp Not Affected
Statement Date: October 30, 2020
| CVE-2020-25681 | Not Affected |
| CVE-2020-25682 | Not Affected |
| CVE-2020-25683 | Not Affected |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Not Affected |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Not Affected |
Vendor Statement
We have not received a statement from the vendor.
Paessler Not Affected
Statement Date: March 28, 2022
| CVE-2020-25681 | Not Affected |
| CVE-2020-25682 | Not Affected |
| CVE-2020-25683 | Not Affected |
| CVE-2020-25684 | Not Affected |
| CVE-2020-25685 | Not Affected |
| CVE-2020-25686 | Not Affected |
| CVE-2020-25687 | Not Affected |
Vendor Statement
We have not received a statement from the vendor.
Peplink Not Affected
Statement Date: September 16, 2021
| CVE-2020-25681 | Not Affected |
| CVE-2020-25682 | Not Affected |
| CVE-2020-25683 | Not Affected |
| CVE-2020-25684 | Not Affected |
| CVE-2020-25685 | Not Affected |
| CVE-2020-25686 | Not Affected |
| CVE-2020-25687 | Not Affected |
Vendor Statement
We have not received a statement from the vendor.
Pulse Secure Not Affected
Statement Date: February 10, 2021
| CVE-2020-25681 | Not Affected |
| CVE-2020-25682 | Not Affected |
| CVE-2020-25683 | Not Affected |
| CVE-2020-25684 | Not Affected |
| CVE-2020-25685 | Not Affected |
| CVE-2020-25686 | Not Affected |
| CVE-2020-25687 | Not Affected |
Vendor Statement
We have not received a statement from the vendor.
Rockwell Automation Not Affected
Statement Date: November 30, 2020
| CVE-2020-25681 | Not Affected |
| CVE-2020-25682 | Not Affected |
| CVE-2020-25683 | Not Affected |
| CVE-2020-25684 | Not Affected |
| CVE-2020-25685 | Not Affected |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Not Affected |
Vendor Statement
We have not received a statement from the vendor.
Treck Not Affected
Statement Date: April 25, 2021
| CVE-2020-25681 | Not Affected |
| CVE-2020-25682 | Not Affected |
| CVE-2020-25683 | Not Affected |
| CVE-2020-25684 | Not Affected |
| CVE-2020-25685 | Not Affected |
| CVE-2020-25686 | Not Affected |
| CVE-2020-25687 | Not Affected |
Vendor Statement
Treck does not use Dnsmasq.
VMware Not Affected
Statement Date: November 03, 2020
| CVE-2020-25681 | Not Affected |
| CVE-2020-25682 | Not Affected |
| CVE-2020-25683 | Not Affected |
| CVE-2020-25684 | Not Affected |
| CVE-2020-25685 | Not Affected |
| CVE-2020-25686 | Not Affected |
| CVE-2020-25687 | Not Affected |
Vendor Statement
We have not received a statement from the vendor.
Ceragon Networks Inc Unknown
Statement Date: January 18, 2021
| CVE-2020-25681 | Unknown |
| Vendor Statement: | |
| not relevant | |
| CVE-2020-25682 | Unknown |
| Vendor Statement: | |
| not relevant | |
| CVE-2020-25683 | Unknown |
| Vendor Statement: | |
| not relevant | |
| CVE-2020-25684 | Unknown |
| Vendor Statement: | |
| not relevant | |
| CVE-2020-25685 | Unknown |
| Vendor Statement: | |
| not relevant | |
| CVE-2020-25686 | Unknown |
| Vendor Statement: | |
| not relevant | |
| CVE-2020-25687 | Unknown |
| Vendor Statement: | |
| not relevant | |
D-Link Systems Inc. Unknown
Statement Date: September 30, 2020
| CVE-2020-25681 | Unknown |
| Vendor Statement: | |
| D-Link has been informed that DNSmasq, a popular caching DNS server and DHCP server, is vulnerable to DNS cache poisoning attacks. We have promptly started our investigation to determine whether D-Link routers are affected, and we will provide updates as soon as we have more information. D-Link takes the issues of network security and user privacy very seriously. We have a dedicated task force and product management team on call to address evolving security issues and implement appropriate security measures. Please check the D-Link website for updates. | |
References:
|
|
| CVE-2020-25682 | Unknown |
| Vendor Statement: | |
| D-Link has been informed that DNSmasq, a popular caching DNS server and DHCP server, is vulnerable to DNS cache poisoning attacks. We have promptly started our investigation to determine whether D-Link routers are affected, and we will provide updates as soon as we have more information. D-Link takes the issues of network security and user privacy very seriously. We have a dedicated task force and product management team on call to address evolving security issues and implement appropriate security measures. Please check the D-Link website for updates. | |
References:
|
|
| CVE-2020-25683 | Unknown |
| Vendor Statement: | |
| D-Link has been informed that DNSmasq, a popular caching DNS server and DHCP server, is vulnerable to DNS cache poisoning attacks. We have promptly started our investigation to determine whether D-Link routers are affected, and we will provide updates as soon as we have more information. D-Link takes the issues of network security and user privacy very seriously. We have a dedicated task force and product management team on call to address evolving security issues and implement appropriate security measures. Please check the D-Link website for updates. | |
References:
|
|
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| Vendor Statement: | |
| D-Link has been informed that DNSmasq, a popular caching DNS server and DHCP server, is vulnerable to DNS cache poisoning attacks. We have promptly started our investigation to determine whether D-Link routers are affected, and we will provide updates as soon as we have more information. D-Link takes the issues of network security and user privacy very seriously. We have a dedicated task force and product management team on call to address evolving security issues and implement appropriate security measures. Please check the D-Link website for updates. | |
References:
|
|
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
D-Link has been informed that DNSmasq, a popular caching DNS server and DHCP server, is vulnerable to DNS cache poisoning attacks. We have promptly started our investigation to determine whether D-Link routers are affected, and we will provide updates as soon as we have more information.
D-Link takes the issues of network security and user privacy very seriously. We have a dedicated task force and product management team on call to address evolving security issues and implement appropriate security measures. Please check the D-Link website for updates.
References
- security@dlink.com
IBM Corporation (zseries) Unknown
Statement Date: September 29, 2020
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
As a best practice for IBM Z, IBM strongly recommends that clients obtain access to the IBM Z and LinuxONE Security Portal and subscribe to the Security Portal’s automatic notification process to get access to the latest service information on security and system integrity related APARs for z/OS and z/VM.
ACCESS Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Actelis Networks Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
ADATA Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
ADTRAN Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Aerohive Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
AhnLab Inc Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
AirWatch Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Akamai Technologies Inc. Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Alcatel-Lucent Enterprise Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Allied Telesis Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Alpine Linux Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Altran Intelligent Systems Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Amazon Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
ANTlabs Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Apple Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Arch Linux Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
ARRIS Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Aruba Networks Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Aspera Inc. Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
ASUSTeK Computer Inc. Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Atheros Communications Inc Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
AT&T Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Avaya Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Belden Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Belkin Inc. Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Bell Canada Enterprises Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
BlackBerry Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
BlueCat Networks Inc. Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Blue Coat Systems Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Blunk Microsystems Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
BoringSSL Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Broadcom Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Buffalo Technology Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
BullGuard Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Cambium Networks Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
CA Technologies Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
CERT-UBIK Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Cesanta Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Cirpack Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
CMX Systems Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Comcast Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Commscope Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Contiki OS Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Cricket Wireless Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Cypress Semiconductor Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
CZ.NIC Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Debian GNU/Linux Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Dell Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Dell EMC Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Dell SecureWorks Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Deutsche Telekom Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Devicescape Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Diebold Election Systems Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
dnsmasq Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
EfficientIP Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
ENEA Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Ericsson Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
European Registry for Internet Domains Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Express Logic Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Extreme Networks Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Fastly Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Fedora Project Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
FNet Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Force10 Networks Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Fortinet Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Foundry Brocade Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
FreeRTOS Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Geexbox Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Gentoo Linux Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
GFI Software Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
GNU adns Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
GNU glibc Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Grandstream Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Green Hills Software Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Hewlett Packard Enterprise Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Hitachi Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Hitron Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Honeywell Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
HP Inc. Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
HTC Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Huawei Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
IBM Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
IBM Numa-Q Division (Formerly Sequent) Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
ICASI Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
InfoExpress Inc. Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Inmarsat Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Internet Systems Consortium Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Internet Systems Consortium - DHCP Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
INTEROP Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
IP Infusion Inc. Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
JH Software Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
JPCERT/CC Vulnerability Handling Team Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Kwikset Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Lancope Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Lantronix Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Lenovo Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
LG Electronics Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
LibreSSL Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Linksys Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
LITE-ON Technology Corporation Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
LiteSpeed Technologies Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Lynx Software Technologies Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
m0n0wall Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Marconi Inc. Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Marvell Semiconductor Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
MaxLinear Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
MediaTek Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Medtronic Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Men & Mice Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Metaswitch Networks Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Micrium Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Microchip Technology Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Micro Focus Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Microsoft Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Minim Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Mitel Networks Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Monroe Electronics Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Motorola Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Muonics Inc. Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
National Cyber Security Center Netherlands Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
National Cyber Security Centre Finland Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
NCSC-FI Vulnerability Coordinator Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
NEC Corporation Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
NetBurner Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
NetComm Wireless Limited Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
NETSCOUT Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
netsnmpj Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
NIKSUN Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Nixu Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
NLnet Labs Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Nokia Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Nominum Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
OleumTech Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
OpenConnect Ltd Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
OpenDNS Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
OpenSSL Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Openwall GNU/*/Linux Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Oracle Corporation Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Oryx Embedded Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Palo Alto Networks Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
pfSense Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Philips Electronics Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
PHPIDS Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
PowerDNS Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Proxim Inc. Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
QLogic Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
QNAP Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Quadros Systems Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Quagga Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Qualcomm Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Quantenna Communications Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Riverbed Technologies Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Roku Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Ruckus Wireless Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Ruijie Networks Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
SafeNet Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Samsung Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Samsung Mobile Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Samsung Semiconductor Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Schneider Electric Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Secure64 Software Corporation Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
SEIKO EPSON Corp. / Epson America Inc. Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Slackware Linux Inc. Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
SMC Networks Inc. Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
SmoothWall Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Snort Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
SonicWall Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Sonos Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Sony Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Sourcefire Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Symantec Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Systech Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
systemd Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
TCPWave Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
TDS Telecom Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Tenable Network Security Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Thales Group Unknown
Statement Date: September 30, 2020
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
TippingPoint Technologies Inc. Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Tizen Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Toshiba Commerce Solutions Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
TP-LINK Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Turbolinux Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Ubee Interactive Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Ubiquiti Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Ubuntu Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Unisys Corporation Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Univention Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Untangle Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Vertical Networks Inc. Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
VMware Carbon Black Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Vultures List Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
WizNET Technology Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
wolfSSL Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Xiaomi Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Xilinx Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Zebra Technologies Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
ZTE Corporation Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
Zyxel Unknown
| CVE-2020-25681 | Unknown |
| CVE-2020-25682 | Unknown |
| CVE-2020-25683 | Unknown |
| CVE-2020-25684 | Unknown |
| CVE-2020-25685 | Unknown |
| CVE-2020-25686 | Unknown |
| CVE-2020-25687 | Unknown |
Vendor Statement
We have not received a statement from the vendor.
References
- https://www.kb.cert.org/vuls/id/800113
- https://kb.cert.org/vuls/id/973527
- https://transition.fcc.gov/bureaus/pshs/advisory/csric3/CSRICIII_9-12-12_WG4-FINAL-Report-DNS-Best-Practices.pdf
- https://astrolavos.gatech.edu/articles/increased_dns_resistance.pdf
- https://www.icann.org/news/blog/security-best-practices-dnssec-validation
- http://www.thekelleys.org.uk/dnsmasq/doc.html
- https://www.jsof-tech.com/disclosures/dnspooq
Other Information
| CVE IDs: | CVE-2020-25681 CVE-2020-25682 CVE-2020-25683 CVE-2020-25684 CVE-2020-25685 CVE-2020-25686 CVE-2020-25687 |
| API URL: | VINCE JSON | CSAF |
| Date Public: | 2021-01-19 |
| Date First Published: | 2021-01-19 |
| Date Last Updated: | 2024-03-04 19:06 UTC |
| Document Revision: | 14 |