CVSS2
Attack Vector
NETWORK
Attack Complexity
MEDIUM
Authentication
NONE
Confidentiality Impact
PARTIAL
Integrity Impact
PARTIAL
Availability Impact
COMPLETE
AV:N/AC:M/Au:N/C:P/I:P/A:C
CVSS3
Attack Vector
NETWORK
Attack Complexity
HIGH
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
HIGH
Integrity Impact
HIGH
Availability Impact
HIGH
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
AI Score
Confidence
High
EPSS
Percentile
96.0%
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.
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.
JSOF also reported vulnerabilities in DNS response validation that can result in DNS cache poisoning.
Note: These cache poisoning scenarios and defenses are discussed in IETF RFC5452.
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.
These vulnerabilities are addressed in dnsmasq 2.83. Users of IoT and embedded devices that use dnsmasq should contact their vendors.
Consider the following security best-practices to protect DNS infrastructure:
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.
434904
Filter by status: All Affected Not Affected Unknown
Filter by content: __ Additional information available
__ Sort by: Status Alphabetical
Expand all
Notified: 2020-09-23 Updated: 2021-01-19
Statement Date: January 04, 2021
CVE-2020-25681 | Not Affected |
---|---|
CVE-2020-25682 | Not Affected CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-24 Updated: 2021-02-08
Statement Date: February 08, 2021
CVE-2020-25681 | Not Affected |
---|---|
CVE-2020-25682 | Not Affected CVE-2020-25683 |
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/
Notified: 2020-09-24 Updated: 2021-01-19
Statement Date: January 02, 2021
CVE-2020-25681 | Not Affected |
---|---|
CVE-2020-25682 | Not Affected CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-24 Updated: 2021-01-19
Statement Date: January 19, 2021
CVE-2020-25681 | Affected |
---|---|
CVE-2020-25682 | Affected CVE-2020-25683 |
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
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
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
Cradlepoint Severity: Critical (dependent upon environment) **Potentially Impacted:**See above **Potential attack paths:**WAN interfaces; Local LAN Associated CVEs: See above
Notified: 2020-09-24 Updated: 2021-01-19
Statement Date: January 11, 2021
CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-24 Updated: 2021-07-20
Statement Date: July 20, 2021
CVE-2020-25681 | Affected |
---|---|
CVE-2020-25682 | Affected CVE-2020-25683 |
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
Notified: 2020-12-15 Updated: 2021-06-02
Statement Date: May 31, 2021
CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
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 ([email protected]).
Notified: 2020-09-25 Updated: 2021-02-08
Statement Date: February 04, 2021
CVE-2020-25681 | Not Affected |
---|---|
CVE-2020-25682 | Not Affected CVE-2020-25683 |
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
Notified: 2020-09-28 Updated: 2023-06-20
Statement Date: June 19, 2023
CVE-2020-25681 | Not Affected |
---|---|
CVE-2020-25682 | Not Affected CVE-2020-25683 |
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.
Notified: 2020-09-28 Updated: 2021-01-19
Statement Date: January 14, 2021
CVE-2020-25681 | Affected |
---|---|
CVE-2020-25682 | Affected CVE-2020-25683 |
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
Notified: 2020-09-28 Updated: 2021-01-19
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 |
Only package dnsmasq-full, which is not installed by default, is affected. | |
CVE-2020-25686 | Affected CVE-2020-25687 |
Only package dnsmasq-full, which is not installed by default, is affected. |
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.
Notified: 2020-10-12 Updated: 2021-01-19
Statement Date: January 11, 2021
CVE-2020-25681 | Affected |
---|---|
CVE-2020-25682 | Affected CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-25 Updated: 2021-01-19
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: |
<https://access.redhat.com/security/cve/cve-2020-25681>
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:
<https://access.redhat.com/security/cve/cve-2020-25682>
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:
<https://access.redhat.com/security/cve/cve-2020-25683>
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:
<https://access.redhat.com/security/cve/cve-2020-25684>
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:
<https://access.redhat.com/security/cve/cve-2020-25685>
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:
<https://access.redhat.com/security/cve/cve-2020-25686>
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:
Notified: 2020-10-12 Updated: 2021-01-19
Statement Date: January 19, 2021
CVE-2020-25681 | Not Affected |
---|---|
CVE-2020-25682 | Not Affected CVE-2020-25683 |
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 ([email protected]).
Notified: 2020-09-28 Updated: 2021-01-20
Statement Date: January 20, 2021
CVE-2020-25681 | Affected |
---|---|
CVE-2020-25682 | Affected CVE-2020-25683 |
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.
Notified: 2020-09-28 Updated: 2021-01-20
Statement Date: January 20, 2021
CVE-2020-25681 | Not Affected |
---|---|
References: |
<https://community.sophos.com/b/security-blog/posts/advisory-resolved-multiple-dnsmasq-vulnerabilities-aka-dnspooq-in-sophos-red>
CVE-2020-25682| Not Affected ** References: **
<https://community.sophos.com/b/security-blog/posts/advisory-resolved-multiple-dnsmasq-vulnerabilities-aka-dnspooq-in-sophos-red>
CVE-2020-25683| Not Affected ** References: **
<https://community.sophos.com/b/security-blog/posts/advisory-resolved-multiple-dnsmasq-vulnerabilities-aka-dnspooq-in-sophos-red>
CVE-2020-25684| Affected ** References: **
<https://community.sophos.com/b/security-blog/posts/advisory-resolved-multiple-dnsmasq-vulnerabilities-aka-dnspooq-in-sophos-red>
CVE-2020-25685| Affected ** References: **
<https://community.sophos.com/b/security-blog/posts/advisory-resolved-multiple-dnsmasq-vulnerabilities-aka-dnspooq-in-sophos-red>
CVE-2020-25686| Affected ** References: **
<https://community.sophos.com/b/security-blog/posts/advisory-resolved-multiple-dnsmasq-vulnerabilities-aka-dnspooq-in-sophos-red>
CVE-2020-25687| Not Affected ** References: **
Sophos Red devices are impacted. More information to follow
Notified: 2020-09-28 Updated: 2021-01-19
Statement Date: January 14, 2021
CVE-2020-25681 | Affected |
---|---|
CVE-2020-25682 | Affected CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-22
Statement Date: January 21, 2021
CVE-2020-25681 | Not Affected |
---|---|
CVE-2020-25682 | Not Affected CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-15 Updated: 2021-01-19
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: |
Notified: 2020-09-29 Updated: 2021-01-19
Statement Date: October 14, 2020
CVE-2020-25681 | Affected |
---|---|
CVE-2020-25682 | Affected CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-29 Updated: 2021-01-19
Statement Date: October 27, 2020
CVE-2020-25681 | Affected |
---|---|
CVE-2020-25682 | Affected CVE-2020-25683 |
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).
Notified: 2020-09-23 Updated: 2021-07-20
Statement Date: June 23, 2021
CVE-2020-25681 | Not Affected |
---|---|
CVE-2020-25682 | Not Affected CVE-2020-25683 |
Dnsmasq is not used in current and supported A10 Networks, Inc products.
Notified: 2020-09-23 Updated: 2021-01-19
Statement Date: January 19, 2021
CVE-2020-25681 | Not Affected |
---|---|
CVE-2020-25682 | Not Affected CVE-2020-25683 |
we do not use dnsmasq in our products
Notified: 2020-09-23 Updated: 2021-01-19
Statement Date: November 02, 2020
CVE-2020-25681 | Not Affected |
---|---|
CVE-2020-25682 | Not Affected CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-23 Updated: 2021-01-19
Statement Date: November 23, 2020
CVE-2020-25681 | Not Affected |
---|---|
CVE-2020-25682 | Not Affected CVE-2020-25683 |
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.
Notified: 2020-09-23 Updated: 2021-01-19
Statement Date: October 30, 2020
CVE-2020-25681 | Not Affected |
---|---|
CVE-2020-25682 | Not Affected CVE-2020-25683 |
AVM does not use dnsmasq | |
CVE-2020-25687 | Not Affected Vendor Statement: |
AVM does not use dnsmasq |
AVM doesn’t use the dnsmasq project within its firmwares.
Notified: 2020-09-23 Updated: 2021-01-19
Statement Date: January 19, 2021
CVE-2020-25681 | Not Affected |
---|---|
CVE-2020-25682 | Not Affected CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-23 Updated: 2021-01-19
Statement Date: October 30, 2020
CVE-2020-25681 | Not Affected |
---|---|
CVE-2020-25682 | Not Affected CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-24 Updated: 2021-01-19
Statement Date: November 25, 2020
CVE-2020-25681 | Not Affected |
---|---|
CVE-2020-25682 | Not Affected CVE-2020-25683 |
No Brocade Fibre Channel Products from Broadcom are currently known to be affected by these vulnerabilities.
Notified: 2020-09-24 Updated: 2021-01-19
Statement Date: November 25, 2020
CVE-2020-25681 | Not Affected |
---|---|
CVE-2020-25682 | Not Affected CVE-2020-25683 |
Do not use/supply Dnsmasq
Notified: 2020-09-24 Updated: 2021-01-19
Statement Date: January 15, 2021
CVE-2020-25681 | Not Affected |
---|---|
CVE-2020-25682 | Not Affected CVE-2020-25683 |
eero products do not use the affected functionality of the affected software products, and so are unaffected by these vulnerabilities.
Notified: 2020-09-24 Updated: 2021-01-20
Statement Date: January 20, 2021
CVE-2020-25681 | Not Affected |
---|---|
CVE-2020-25682 | Not Affected CVE-2020-25683 |
Espressif doesn’t use dnsmasq in any product SDKs or other published software, so is not affected.
Notified: 2020-09-24 Updated: 2021-01-19
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. |
The package dnsmasq and/or associated binaries are not installed on F5 products, therefore they are not affected by these vulnerabilities.
Notified: 2020-09-24 Updated: 2021-01-19
Statement Date: September 24, 2020
CVE-2020-25681 | Not Affected |
---|---|
CVE-2020-25682 | Not Affected CVE-2020-25683 |
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.
Notified: 2020-09-24 Updated: 2021-10-06
Statement Date: June 24, 2021
CVE-2020-25681 | Not Affected |
---|---|
CVE-2020-25682 | Not Affected CVE-2020-25683 |
Not Affected.
Notified: 2020-09-24 Updated: 2021-01-19
Statement Date: December 07, 2020
CVE-2020-25681 | Not Affected |
---|---|
CVE-2020-25682 | Not Affected CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-24 Updated: 2021-01-19
Statement Date: November 26, 2020
CVE-2020-25681 | Not Affected |
---|---|
CVE-2020-25682 | Not Affected CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-25 Updated: 2021-01-19
Statement Date: October 16, 2020
CVE-2020-25681 | Not Affected |
---|---|
CVE-2020-25682 | Not Affected CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-25 Updated: 2021-01-19
Statement Date: January 19, 2021
CVE-2020-25681 | Not Affected |
---|---|
CVE-2020-25682 | Not Affected CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-25 Updated: 2021-01-19
Statement Date: January 14, 2021
CVE-2020-25681 | Not Affected |
---|---|
CVE-2020-25682 | Not Affected CVE-2020-25683 |
LANCOM Systems products are not affected by these vulnerabilities.
Notified: 2020-09-25 Updated: 2024-08-19
Statement Date: August 07, 2024
CVE-2020-25681 | Not Affected |
---|---|
CVE-2020-25682 | Not Affected CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-25 Updated: 2021-01-19
Statement Date: December 04, 2020
CVE-2020-25681 | Not Affected |
---|---|
CVE-2020-25682 | Not Affected CVE-2020-25683 |
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.
Notified: 2020-09-23 Updated: 2021-01-19
Statement Date: September 24, 2020
CVE-2020-25681 | Not Affected |
---|---|
CVE-2020-25682 | Not Affected CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-06-02
Statement Date: May 17, 2021
CVE-2020-25681 | Not Affected |
---|---|
CVE-2020-25682 | Not Affected CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19
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 |
Dnsmasq not used in MikroTik software | |
CVE-2020-25686 | Unknown CVE-2020-25687 |
Dnsmasq not used in MikroTik software
Notified: 2020-09-28 Updated: 2021-01-19
Statement Date: January 19, 2021
CVE-2020-25681 | Not Affected |
---|---|
CVE-2020-25682 | Not Affected CVE-2020-25683 |
dnsmasq is not used.
Notified: 2020-09-28 Updated: 2021-01-19
Statement Date: October 30, 2020
CVE-2020-25681 | Not Affected |
---|---|
CVE-2020-25682 | Not Affected CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2022-11-21
Statement Date: March 28, 2022
CVE-2020-25681 | Not Affected |
---|---|
CVE-2020-25682 | Not Affected CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-10-06
Statement Date: September 16, 2021
CVE-2020-25681 | Not Affected |
---|---|
CVE-2020-25682 | Not Affected CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-02-11
Statement Date: February 10, 2021
CVE-2020-25681 | Not Affected |
---|---|
CVE-2020-25682 | Not Affected CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19
Statement Date: November 30, 2020
CVE-2020-25681 | Not Affected |
---|---|
CVE-2020-25682 | Not Affected CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-29 Updated: 2021-06-02
Statement Date: April 25, 2021
CVE-2020-25681 | Not Affected |
---|---|
CVE-2020-25682 | Not Affected CVE-2020-25683 |
Treck does not use Dnsmasq.
Notified: 2020-09-29 Updated: 2021-01-19
Statement Date: November 03, 2020
CVE-2020-25681 | Not Affected |
---|---|
CVE-2020-25682 | Not Affected CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-24 Updated: 2021-01-19
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 |
Notified: 2020-09-24 Updated: 2021-01-19
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: |
[email protected]
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:
[email protected]
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:
[email protected]
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:
[email protected]
CVE-2020-25686| Unknown CVE-2020-25687| Unknown
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.
Notified: 2020-09-25 Updated: 2021-01-19
Statement Date: September 29, 2020
CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
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.
Notified: 2020-09-23 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-23 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-23 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-23 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-23 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-23 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-23 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-23 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-23 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-23 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-23 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-23 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-23 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-23 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-23 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-23 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-23 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-23 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-23 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-23 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-23 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-23 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-23 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-23 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-23 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-23 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-23 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-23 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-23 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-23 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-23 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-24 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-24 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-24 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-24 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-24 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-24 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-24 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-24 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-24 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-24 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-24 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-24 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-24 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-24 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-24 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-24 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-24 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-24 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-24 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-24 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-24 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-18 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-24 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-24 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-24 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-24 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-24 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-24 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-24 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-24 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-24 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-24 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-24 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-24 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-24 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-24 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-24 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-24 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-24 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-24 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-24 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-24 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-24 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-24 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2021-01-19 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-25 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-25 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-25 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-25 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-25 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-25 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-25 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-25 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-25 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-25 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-25 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-25 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-25 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-25 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-25 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-25 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-25 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-25 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-25 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-25 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-25 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-25 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-25 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-25 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2021-01-13 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2021-01-19 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-29 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-29 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-10-08 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-12-08 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-28 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-29 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-29 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-29 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-29 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-29 Updated: 2021-01-19
Statement Date: September 30, 2020
CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-29 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-29 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-29 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-29 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-29 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2021-01-19 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-29 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-29 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-29 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-29 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-29 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-29 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-25 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-29 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-29 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-29 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-29 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-29 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-29 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-29 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-29 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
Notified: 2020-09-29 Updated: 2021-01-19 CVE-2020-25681 | Unknown |
---|---|
CVE-2020-25682 | Unknown CVE-2020-25683 |
We have not received a statement from the vendor.
View all 253 vendors __View less vendors __
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 |
Date Public: | 2021-01-19 Date First Published: |
www.thekelleys.org.uk/dnsmasq/doc.html
astrolavos.gatech.edu/articles/increased_dns_resistance.pdf
kb.cert.org/vuls/id/973527
transition.fcc.gov/bureaus/pshs/advisory/csric3/CSRICIII_9-12-12_WG4-FINAL-Report-DNS-Best-Practices.pdf
www.icann.org/news/blog/security-best-practices-dnssec-validation
www.jsof-tech.com/disclosures/dnspooq
www.kb.cert.org/vuls/id/800113
CVSS2
Attack Vector
NETWORK
Attack Complexity
MEDIUM
Authentication
NONE
Confidentiality Impact
PARTIAL
Integrity Impact
PARTIAL
Availability Impact
COMPLETE
AV:N/AC:M/Au:N/C:P/I:P/A:C
CVSS3
Attack Vector
NETWORK
Attack Complexity
HIGH
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
HIGH
Integrity Impact
HIGH
Availability Impact
HIGH
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
AI Score
Confidence
High
EPSS
Percentile
96.0%