9.8 High
CVSS3
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
HIGH
Integrity Impact
HIGH
Availability Impact
HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
7.5 High
CVSS2
Access Vector
NETWORK
Access Complexity
LOW
Authentication
NONE
Confidentiality Impact
PARTIAL
Integrity Impact
PARTIAL
Availability Impact
PARTIAL
AV:N/AC:L/Au:N/C:P/I:P/A:P
0.859 High
EPSS
Percentile
98.5%
Multiple open-source embedded TCP/IP stacks, commonly used in Internet of Things (IoT) and embedded devices, have several vulnerabilities stemming from improper memory management. These vulnerabilities are also tracked as ICS-VU-633937 and JVNVU#96491057 as well as the name AMNESIA:33.
Embedded TCP/IP stacks provide essential network communication capability using TCP/IP networking to many lightweight operating systems adopted by IoT and other embedded devices. These software stacks can also be used in the latest technologies such as Edge Computing. The following embedded TCP/IP stacks were discovered to have 33 memory related vulnerabilities included in this advisory:
These networking software stacks can be integrated in various ways, including compiled from source, modified and integrated, and linked as a dynamic or static libraries, allowing for a wide variety of implementations. As an example, projects such as Apache Nuttx and open-iscsi have adopted common libraries and software modules, thus inheriting some of these vulnerabilities with varying levels of impact. The diversity of implementations and the lack of supply chain visibility has made it difficult to accurately assess the impact, usage as well as the potential exploitability of these vulnerabilities.
In general, most of these vulnerabilities are caused by memory management bugs, commonly seen in lightweight software implementations in Real Time Operating Systems (RTOS) and IoT devices. For specific details on these vulnerabilities, see the Forescout advisory that provides technical details. Due to the lack of visibility of these software usage, Forescout has released an open source version of Detector that can be used to identify potentially vulnerable software.
The impact of these vulnerabilities vary widely due to the combination of build and runtime options customized while including these in embedded devices. In summary, a remote, unauthenticated attacker may be able to use specially-crafted network packets to cause the vulnerable device to behave in unexpected ways such as a failure (denial of service), disclosure of private information, or execution of arbitrary code.
Update to the latest stable version of the affected embedded TCP/IP software that address these recently disclosed vulnerabilities. If you have adopted this software from an upstream provider, contact the provider to get appropriate updates that need to be integrated into your software. Concerned end-users of IoT and embedded devices that implement these vulnerable TCP/IP software stacks should contact their vendor or the closest reseller to obtain appropriate updates.
We recommend that you follow best practices when connecting IoT or embedded devices to a network:
Jos Wetzels, Stanislav Dashevskyi, Amine Amri and Daniel dos Santos of Forescout Technologies researched and reported these vulnerabilities.
This document was written by Vijay Sarvepalli.
815128
Filter by status: All Affected Not Affected Unknown
Filter by content: __ Additional information available
__ Sort by: Status Alphabetical
Expand all
Notified: 2020-12-09 Updated: 2020-12-09
Statement Date: December 08, 2020
CVE-2020-13984 | Not Affected |
---|---|
CVE-2020-13985 | Affected CVE-2020-13986 |
Cyanconnode is aware of multiple security vulnerabilities in the uIP stack - commonly referred to as “AMNESIA:33”. The Cyan Technlogy IDE, CyanIDE, was distributed with uIP v1.0. The final release of CyanIDE before it reached end-of-life was v2.4.0 in 2014. Therefore, we deem the exploitation of our product a low risk. Patches won’t be provided since the affected product is end-of-life.
Notified: 2020-08-24 Updated: 2021-02-16
Statement Date: February 16, 2021
CVE-2020-13984 | Not Affected |
---|---|
CVE-2020-13985 | Not Affected CVE-2020-13986 |
All mentioned vulnerabilities were solved in previous FNET v4.7.0 release.
FNET has their latest repository at Github https://github.com/butok/FNET/ Their latest release is 4.7.1 linked in the References.
Notified: 2020-08-28 Updated: 2020-12-08
Statement Date: December 02, 2020
CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
Microchip is aware of a TCP/IP security vulnerability known as Amnesia:33. Microchip takes security issues seriously and is currently working to mitigate the issues and provide solutions for our clients. We have determined that some CVEs affect some of our networking products. For details on impacted products and resolution plans, visit below URL.
Notified: 2020-08-21 Updated: 2021-03-23
Statement Date: March 19, 2021
CVE-2020-13984 | Not Affected |
---|---|
CVE-2020-13985 | Not Affected CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-15 Updated: 2020-12-14
Statement Date: December 14, 2020
CVE-2020-13984 | Not Affected |
---|---|
CVE-2020-13985 | Not Affected CVE-2020-13986 |
our open-iscsi package is affected by this uIP issue | |
CVE-2020-13988 | Affected Vendor Statement: |
Our open-iscsi package be affected by this issue. | |
CVE-2020-17437 | Affected Vendor Statement: |
our open-iscsi package is affected by this issue. | |
CVE-2020-17438 | Affected Vendor Statement: |
our open-iscsi package is affected by this issue. | |
CVE-2020-17439 | Not Affected CVE-2020-17440 |
The Linux Kernel TCP/IP stack used by SUSE Linux Enterprise and openSUSE is not affected by the listed vulnerabilities.
SUSE ships open-iscsi, which embeds a version of the uIP IP stack, which is affected by some of the vulnerabilities, and will provide fixes.
Notified: 2020-10-28 Updated: 2021-03-23
Statement Date: March 18, 2021
CVE-2020-13984 | Not Affected |
---|---|
CVE-2020-13985 | Not Affected CVE-2020-13986 |
Siemens is aware of the security vulnerabilities in several TCP/IP stacks, also named “AMNESIA:33” and disclosed on 2020-12-08. The impact to Siemens products is described in the Security Advisories SSA-541017, published on 2020-12-08 and SSA-541018, published on 2021-03-09 on the Siemens ProductCERT page (https://www.siemens.com/cert/advisories).
Notified: 2020-12-09 Updated: 2020-12-09
Statement Date: December 08, 2020
CVE-2020-13984 | Affected |
---|---|
CVE-2020-13985 | Affected CVE-2020-13986 |
Weinert-automation is aware of multiple security vulnerabilities in the uIP stack - commonly referred to as “AMNESIA:33”. The stack was used in weAut_01 (software weAutSys) which was discontinued in 2012 and is verifiably not in use anymore. Therefore, we deem the exploitation of our product a low risk. Patches won’t be provided since the product is end-of-life.
Notified: 2020-09-15 Updated: 2020-12-21 CVE-2020-13984 | Not Affected |
---|---|
CVE-2020-13985 | Not Affected CVE-2020-13986 |
We have not received a statement from the vendor.
https://github.com/open-iscsi/open-iscsi/security/advisories/GHSA-r278-fm99-8rgp
Notified: 2020-08-24 Updated: 2020-12-08
Statement Date: September 24, 2020
CVE-2020-13984 | Not Affected |
---|---|
CVE-2020-13985 | Not Affected CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2021-02-04 Updated: 2021-03-23
Statement Date: March 22, 2021
CVE-2020-13984 | Not Affected |
---|---|
CVE-2020-13985 | Not Affected CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-12-02 Updated: 2020-12-08 CVE-2020-13984 | Not Affected |
---|---|
CVE-2020-13985 | Not Affected CVE-2020-13986 |
We have not received a statement from the vendor.
Statement provided by Abbott labs available at ICS-CERT advisory
Notified: 2020-08-24 Updated: 2020-12-08
Statement Date: December 07, 2020
CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-24 Updated: 2020-12-08
Statement Date: December 07, 2020
CVE-2020-13984 | Not Affected |
---|---|
CVE-2020-13985 | Not Affected CVE-2020-13986 |
Arista Networks does not use the affected software in any of its product lines.
Notified: 2020-12-09 Updated: 2021-01-06
Statement Date: January 06, 2021
CVE-2020-13984 | Not Affected |
---|---|
CVE-2020-13985 | Not Affected CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-25 Updated: 2020-12-08
Statement Date: September 16, 2020
CVE-2020-13984 | Not Affected |
---|---|
CVE-2020-13985 | Not Affected CVE-2020-13986 |
Barracuda does not use these libraries in any of our products.
Notified: 2020-08-20 Updated: 2021-03-23
Statement Date: March 22, 2021
CVE-2020-13984 | Not Affected |
---|---|
CVE-2020-13985 | Not Affected CVE-2020-13986 |
Belden devices do not contain the vulnerable software and are not affected by this vulnerability.
Notified: 2020-08-26 Updated: 2020-12-08
Statement Date: September 21, 2020
CVE-2020-13984 | Not Affected |
---|---|
CVE-2020-13985 | Not Affected CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-26 Updated: 2021-03-23
Statement Date: March 18, 2021
CVE-2020-13984 | Not Affected |
---|---|
Vendor Statement: | |
No Brocade Fibre Channel Products from Broadcom are currently known to be affected by this vulnerability. | |
CVE-2020-13985 | Not Affected Vendor Statement: |
No Brocade Fibre Channel Products from Broadcom are currently known to be affected by this vulnerability. | |
CVE-2020-13986 | Not Affected Vendor Statement: |
No Brocade Fibre Channel Products from Broadcom are currently known to be affected by this vulnerability. | |
CVE-2020-13987 | Not Affected Vendor Statement: |
No Brocade Fibre Channel Products from Broadcom are currently known to be affected by this vulnerability. | |
CVE-2020-13988 | Not Affected Vendor Statement: |
No Brocade Fibre Channel Products from Broadcom are currently known to be affected by this vulnerability. | |
CVE-2020-17437 | Not Affected Vendor Statement: |
No Brocade Fibre Channel Products from Broadcom are currently known to be affected by this vulnerability. | |
CVE-2020-17438 | Not Affected Vendor Statement: |
No Brocade Fibre Channel Products from Broadcom are currently known to be affected by this vulnerability. | |
CVE-2020-17439 | Not Affected Vendor Statement: |
No Brocade Fibre Channel Products from Broadcom are currently known to be affected by this vulnerability. | |
CVE-2020-17440 | Not Affected Vendor Statement: |
No Brocade Fibre Channel Products from Broadcom are currently known to be affected by this vulnerability. | |
CVE-2020-17441 | Not Affected Vendor Statement: |
No Brocade Fibre Channel Products from Broadcom are currently known to be affected by this vulnerability. | |
CVE-2020-17442 | Not Affected Vendor Statement: |
No Brocade Fibre Channel Products from Broadcom are currently known to be affected by this vulnerability. | |
CVE-2020-17443 | Not Affected Vendor Statement: |
No Brocade Fibre Channel Products from Broadcom are currently known to be affected by this vulnerability. | |
CVE-2020-17444 | Not Affected Vendor Statement: |
No Brocade Fibre Channel Products from Broadcom are currently known to be affected by this vulnerability. | |
CVE-2020-17445 | Not Affected Vendor Statement: |
No Brocade Fibre Channel Products from Broadcom are currently known to be affected by this vulnerability. | |
CVE-2020-17467 | Not Affected Vendor Statement: |
No Brocade Fibre Channel Products from Broadcom are currently known to be affected by this vulnerability. | |
CVE-2020-17468 | Not Affected Vendor Statement: |
No Brocade Fibre Channel Products from Broadcom are currently known to be affected by this vulnerability. | |
CVE-2020-17469 | Not Affected Vendor Statement: |
No Brocade Fibre Channel Products from Broadcom are currently known to be affected by this vulnerability. | |
CVE-2020-17470 | Not Affected Vendor Statement: |
No Brocade Fibre Channel Products from Broadcom are currently known to be affected by this vulnerability. | |
CVE-2020-24334 | Not Affected Vendor Statement: |
No Brocade Fibre Channel Products from Broadcom are currently known to be affected by this vulnerability. | |
CVE-2020-24335 | Not Affected Vendor Statement: |
No Brocade Fibre Channel Products from Broadcom are currently known to be affected by this vulnerability. | |
CVE-2020-24336 | Not Affected Vendor Statement: |
No Brocade Fibre Channel Products from Broadcom are currently known to be affected by this vulnerability. | |
CVE-2020-24337 | Not Affected Vendor Statement: |
No Brocade Fibre Channel Products from Broadcom are currently known to be affected by this vulnerability. | |
CVE-2020-24338 | Not Affected Vendor Statement: |
No Brocade Fibre Channel Products from Broadcom are currently known to be affected by this vulnerability. | |
CVE-2020-24339 | Not Affected Vendor Statement: |
No Brocade Fibre Channel Products from Broadcom are currently known to be affected by this vulnerability. | |
CVE-2020-24340 | Not Affected Vendor Statement: |
No Brocade Fibre Channel Products from Broadcom are currently known to be affected by this vulnerability. | |
CVE-2020-24341 | Not Affected Vendor Statement: |
No Brocade Fibre Channel Products from Broadcom are currently known to be affected by this vulnerability. | |
CVE-2020-24383 | Not Affected Vendor Statement: |
No Brocade Fibre Channel Products from Broadcom are currently known to be affected by this vulnerability. | |
CVE-2020-25107 | Not Affected CVE-2020-25108 |
Notified: 2020-08-28 Updated: 2020-12-08
Statement Date: December 08, 2020
CVE-2020-13984 | Not Affected |
---|---|
CVE-2020-13985 | Not Affected CVE-2020-13986 |
Not affected by this case
Notified: 2020-12-23 Updated: 2021-03-23
Statement Date: March 21, 2021
CVE-2020-13984 | Not Affected |
---|---|
CVE-2020-13985 | Not Affected CVE-2020-13986 |
Check Point is not affected by these vulnerabilities.
Notified: 2020-08-20 Updated: 2021-03-23
Statement Date: March 22, 2021
CVE-2020-13984 | Not Affected |
---|---|
CVE-2020-13985 | Not Affected CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-31 Updated: 2020-12-14
Statement Date: December 11, 2020
CVE-2020-13984 | Not Affected |
---|---|
CVE-2020-13985 | Not Affected CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-20 Updated: 2020-12-14
Statement Date: December 09, 2020
CVE-2020-13984 | Not Affected |
---|---|
CVE-2020-13985 | Not Affected CVE-2020-13986 |
We do not use any of the affected stacks in our products. https://www.digi.com/resources/security
Notified: 2020-09-09 Updated: 2021-01-13
Statement Date: January 12, 2021
CVE-2020-13984 | Not Affected |
---|---|
CVE-2020-13985 | Not Affected CVE-2020-13986 |
Espressif ESP8266 SDKs and ESP-IDF (SDK for ESP32 and ESP32-S2) both use the TCP/IP library lwIP, therefore are not affected by these vulnerabilities.
Notified: 2020-08-21 Updated: 2020-12-08
Statement Date: December 08, 2020
CVE-2020-13984 | Not Affected |
---|---|
Vendor Statement: | |
F5 firmware (BIOS, LOP, BMC, LCD) does not use these products. | |
CVE-2020-13985 | Not Affected Vendor Statement: |
F5 firmware (BIOS, LOP, BMC, LCD) does not use these products. | |
CVE-2020-13986 | Not Affected Vendor Statement: |
F5 firmware (BIOS, LOP, BMC, LCD) does not use these products. | |
CVE-2020-13987 | Not Affected Vendor Statement: |
F5 firmware (BIOS, LOP, BMC, LCD) does not use these products. | |
CVE-2020-13988 | Not Affected Vendor Statement: |
F5 firmware (BIOS, LOP, BMC, LCD) does not use these products. | |
CVE-2020-17437 | Not Affected Vendor Statement: |
F5 firmware (BIOS, LOP, BMC, LCD) does not use these products. | |
CVE-2020-17438 | Not Affected Vendor Statement: |
F5 firmware (BIOS, LOP, BMC, LCD) does not use these products. | |
CVE-2020-17439 | Not Affected Vendor Statement: |
F5 firmware (BIOS, LOP, BMC, LCD) does not use these products. | |
CVE-2020-17440 | Not Affected Vendor Statement: |
F5 firmware (BIOS, LOP, BMC, LCD) does not use these products. | |
CVE-2020-17441 | Not Affected Vendor Statement: |
F5 firmware (BIOS, LOP, BMC, LCD) does not use these products. | |
CVE-2020-17442 | Not Affected Vendor Statement: |
F5 firmware (BIOS, LOP, BMC, LCD) does not use these products. | |
CVE-2020-17443 | Not Affected Vendor Statement: |
F5 firmware (BIOS, LOP, BMC, LCD) does not use these products. | |
CVE-2020-17444 | Not Affected Vendor Statement: |
F5 firmware (BIOS, LOP, BMC, LCD) does not use these products. | |
CVE-2020-17445 | Not Affected Vendor Statement: |
F5 firmware (BIOS, LOP, BMC, LCD) does not use these products. | |
CVE-2020-17467 | Not Affected Vendor Statement: |
F5 firmware (BIOS, LOP, BMC, LCD) does not use these products. | |
CVE-2020-17468 | Not Affected Vendor Statement: |
F5 firmware (BIOS, LOP, BMC, LCD) does not use these products. | |
CVE-2020-17469 | Not Affected Vendor Statement: |
F5 firmware (BIOS, LOP, BMC, LCD) does not use these products. | |
CVE-2020-17470 | Not Affected Vendor Statement: |
F5 firmware (BIOS, LOP, BMC, LCD) does not use these products. | |
CVE-2020-24334 | Not Affected Vendor Statement: |
F5 firmware (BIOS, LOP, BMC, LCD) does not use these products. | |
CVE-2020-24335 | Not Affected Vendor Statement: |
F5 firmware (BIOS, LOP, BMC, LCD) does not use these products. | |
CVE-2020-24336 | Not Affected Vendor Statement: |
F5 firmware (BIOS, LOP, BMC, LCD) does not use these products. | |
CVE-2020-24337 | Not Affected Vendor Statement: |
F5 firmware (BIOS, LOP, BMC, LCD) does not use these products. | |
CVE-2020-24338 | Not Affected Vendor Statement: |
F5 firmware (BIOS, LOP, BMC, LCD) does not use these products. | |
CVE-2020-24339 | Not Affected Vendor Statement: |
F5 firmware (BIOS, LOP, BMC, LCD) does not use these products. | |
CVE-2020-24340 | Not Affected Vendor Statement: |
F5 firmware (BIOS, LOP, BMC, LCD) does not use these products. | |
CVE-2020-24341 | Not Affected Vendor Statement: |
F5 firmware (BIOS, LOP, BMC, LCD) does not use these products. | |
CVE-2020-24383 | Not Affected Vendor Statement: |
F5 firmware (BIOS, LOP, BMC, LCD) does not use these products. | |
CVE-2020-25107 | Not Affected CVE-2020-25108 |
F5 firmware (BIOS, LOP, BMC, LCD) does not use these products.
Notified: 2020-08-28 Updated: 2020-12-08
Statement Date: December 07, 2020
CVE-2020-13984 | Not Affected |
---|---|
CVE-2020-13985 | Not Affected CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-12-02 Updated: 2020-12-08
Statement Date: December 07, 2020
CVE-2020-13984 | Not Affected |
---|---|
CVE-2020-13985 | Not Affected CVE-2020-13986 |
Based on our review, we can confirm that Fitbit is not affected by the “Amnesia” IoT TCP/IP stack vulnerabilities identified by the team at Forescout Technologies.
Fitbit statement was provided to ICS-CERT
Notified: 2020-09-09 Updated: 2020-12-16
Statement Date: December 16, 2020
CVE-2020-13984 | Not Affected |
---|---|
CVE-2020-13985 | Not Affected CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-28 Updated: 2020-12-08
Statement Date: September 25, 2020
CVE-2020-13984 | Not Affected |
---|---|
CVE-2020-13985 | Not Affected CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-09 Updated: 2020-12-08
Statement Date: December 08, 2020
CVE-2020-13984 | Not Affected |
---|---|
CVE-2020-13985 | Not Affected CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-28 Updated: 2020-12-08
Statement Date: September 16, 2020
CVE-2020-13984 | Not Affected |
---|---|
CVE-2020-13985 | Not Affected CVE-2020-13986 |
Our products have none of the embedded software listed in this case.
Notified: 2020-08-20 Updated: 2021-01-11
Statement Date: January 11, 2021
CVE-2020-13984 | Not Affected |
---|---|
CVE-2020-13985 | Not Affected CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-20 Updated: 2020-12-08
Statement Date: September 02, 2020
CVE-2020-13984 | Not Affected |
---|---|
Vendor Statement: | |
Juniper Networks products do not use Contiki-OS, thus we are not affected. | |
CVE-2020-13985 | Not Affected Vendor Statement: |
Juniper Networks products do not use Contiki-OS, thus we are not affected. | |
CVE-2020-13986 | Not Affected Vendor Statement: |
Juniper Networks products do not use Contiki-OS, thus we are not affected. | |
CVE-2020-13987 | Not Affected Vendor Statement: |
Juniper Networks products do not use uIP, thus we are not affected. | |
CVE-2020-13988 | Not Affected Vendor Statement: |
Juniper Networks products do not use Contiki-OS, thus we are not affected. | |
CVE-2020-17437 | Not Affected Vendor Statement: |
Juniper Networks products do not use Contiki-OS, thus we are not affected. | |
CVE-2020-17438 | Not Affected Vendor Statement: |
Juniper Networks products do not use uIP, thus we are not affected. | |
CVE-2020-17439 | Not Affected Vendor Statement: |
Juniper Networks products do not use uIP, thus we are not affected. | |
CVE-2020-17440 | Not Affected Vendor Statement: |
Juniper Networks products do not use uIP, thus we are not affected. | |
CVE-2020-17441 | Not Affected Vendor Statement: |
Juniper Networks products do not use PicoTCP nor PicoTCP-NG, thus we are not affected. | |
CVE-2020-17442 | Not Affected Vendor Statement: |
Juniper Networks products do not use PicoTCP nor PicoTCP-NG, thus we are not affected. | |
CVE-2020-17443 | Not Affected Vendor Statement: |
Juniper Networks products do not use PicoTCP nor PicoTCP-NG, thus we are not affected. | |
CVE-2020-17444 | Not Affected Vendor Statement: |
Juniper Networks products do not use PicoTCP and PicoTCP-NG, thus we are not affected. | |
CVE-2020-17445 | Not Affected Vendor Statement: |
Juniper Networks products do not use PicoTCP nor PicoTCP-NG, thus we are not affected. | |
CVE-2020-17467 | Not Affected Vendor Statement: |
Juniper Networks products do not use Fnet, thus we are not affected. | |
CVE-2020-17468 | Not Affected Vendor Statement: |
Juniper Networks products do not use Fnet, thus we are not affected. | |
CVE-2020-17469 | Not Affected Vendor Statement: |
Juniper Networks products do not use Fnet, thus we are not affected. | |
CVE-2020-17470 | Not Affected Vendor Statement: |
Juniper Networks products do not use Fnet, thus we are not affected. | |
CVE-2020-24334 | Not Affected Vendor Statement: |
Juniper Networks products do not use Contiki-OS, thus we are not affected. | |
CVE-2020-24335 | Unknown CVE-2020-24336 |
Juniper Networks products do not use Contiki-OS, thus we are not affected. | |
CVE-2020-24337 | Not Affected Vendor Statement: |
Juniper Networks products do not use PicoTCP nor PicoTCP-NG, thus we are not affected. | |
CVE-2020-24338 | Unknown CVE-2020-24339 |
Juniper Networks products do not use PicoTCP nor PicoTCP-NG, thus we are not affected. | |
CVE-2020-24341 | Not Affected Vendor Statement: |
Juniper Networks products do not use PicoTCP nor PicoTCP-NG, thus we are not affected. | |
CVE-2020-24383 | Not Affected Vendor Statement: |
Juniper Networks products do not use Fnet, thus we are not affected. | |
CVE-2020-25107 | Unknown CVE-2020-25108 |
Notified: 2020-08-28 Updated: 2021-01-28
Statement Date: January 19, 2021
CVE-2020-13984 | Not Affected |
---|---|
CVE-2020-13985 | Not Affected CVE-2020-13986 |
miredo uses adhoc code for ICMPv6; is not involved with DNS.
Notified: 2020-08-28 Updated: 2020-12-08
Statement Date: September 03, 2020
CVE-2020-13984 | Not Affected |
---|---|
CVE-2020-13985 | Not Affected CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-25 Updated: 2021-05-11
Statement Date: April 13, 2021
CVE-2020-13984 | Not Affected |
---|---|
CVE-2020-13985 | Not Affected CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-12-15 Updated: 2021-03-23
Statement Date: March 19, 2021
CVE-2020-13984 | Not Affected |
---|---|
CVE-2020-13985 | Not Affected CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-21
Statement Date: December 21, 2020
CVE-2020-13984 | Not Affected |
---|---|
CVE-2020-13985 | Not Affected CVE-2020-13986 |
Sophos products and services are not impacted by these vulnerabilities.
Notified: 2020-08-28 Updated: 2020-12-08
Statement Date: September 14, 2020
CVE-2020-13984 | Not Affected |
---|---|
CVE-2020-13985 | Not Affected CVE-2020-13986 |
Vmware is not affected by these issues directly.
Notified: 2020-08-28 Updated: 2020-12-08
Statement Date: September 09, 2020
CVE-2020-13984 | Not Affected |
---|---|
CVE-2020-13985 | Not Affected CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-25 Updated: 2020-12-08
Statement Date: October 14, 2020
CVE-2020-13984 | Not Affected |
---|---|
CVE-2020-13985 | Not Affected CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-25 Updated: 2020-12-08
Statement Date: September 11, 2020
CVE-2020-13984 | Not Affected |
---|---|
CVE-2020-13985 | Not Affected CVE-2020-13986 |
Xilinx is not affected by these vulnerabilities.
Notified: 2020-08-28 Updated: 2021-01-28 CVE-2020-13984 | Not Affected |
---|---|
CVE-2020-13985 | Not Affected CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08
Statement Date: October 05, 2020
CVE-2020-13984 | Not Affected |
---|---|
CVE-2020-13985 | Not Affected CVE-2020-13986 |
The affected code is not used in the Zephyr TCP implementation.
Notified: 2020-08-21 Updated: 2020-12-09
Statement Date: December 09, 2020
CVE-2020-13984 | Not Affected |
---|---|
CVE-2020-13985 | Not Affected CVE-2020-13986 |
Zyxel is NOT affected because our products don’t make use of these TCP/IP software
Notified: 2020-12-02 Updated: 2020-12-08
Statement Date: December 08, 2020
CVE-2020-13984 | Not Affected |
---|---|
CVE-2020-13985 | Not Affected CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-24 Updated: 2021-05-11
Statement Date: April 06, 2021
CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-12-02 Updated: 2021-03-15
Statement Date: January 21, 2021
CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Please visit Texas Instrument PSIRT anouncement on AMNESIA:33 vulnerabilities. https://www.ti.com/lit/ml/sszo001/sszo001.pdf?ts=1615806156409
Notified: 2020-09-07 Updated: 2020-12-17 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Note that M0n0wall is end-of-life http://forum.m0n0.ch/forum/topic,6369.0.html https://m0n0.ch/wall/mailinglist.php
Administrator of this software, Manuel Kasper, recommends you move to OPNSense
Notified: 2020-08-24 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-24 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-24 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-24 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-24 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-24 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-24 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-20 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-11-02 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-10-02 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-24 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-24 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-26 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-26 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-26 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-26 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-26 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-28 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-28 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-28 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-12-02 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-20 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-28 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-28 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-28 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-24 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-31 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-31 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-20 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-31 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-31 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-31 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-31 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-31 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-31 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-31 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-16 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-21 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-28 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-09 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-09 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-25 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-25 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-09 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-09 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-25 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-09 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-25 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-09 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-09 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-28 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-28 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-28 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-28 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-28 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-28 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-09 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-20 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-20 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-21 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-10-08 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-08-25 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-12-08 Updated: 2020-12-09 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-10-26 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-12-10 Updated: 2020-12-14 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-12-10 Updated: 2020-12-14 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-12-02 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-12-02 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
Notified: 2020-09-07 Updated: 2020-12-08 CVE-2020-13984 | Unknown |
---|---|
CVE-2020-13985 | Unknown CVE-2020-13986 |
We have not received a statement from the vendor.
View all 174 vendors __View less vendors __
9.8 High
CVSS3
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
HIGH
Integrity Impact
HIGH
Availability Impact
HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
7.5 High
CVSS2
Access Vector
NETWORK
Access Complexity
LOW
Authentication
NONE
Confidentiality Impact
PARTIAL
Integrity Impact
PARTIAL
Availability Impact
PARTIAL
AV:N/AC:L/Au:N/C:P/I:P/A:P
0.859 High
EPSS
Percentile
98.5%