8.8 High
CVSS3
Attack Vector
ADJACENT_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:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
8.3 High
CVSS2
Access Vector
ADJACENT_NETWORK
Access Complexity
LOW
Authentication
NONE
Confidentiality Impact
COMPLETE
Integrity Impact
COMPLETE
Availability Impact
COMPLETE
AV:A/AC:L/Au:N/C:C/I:C/A:C
0.009 Low
EPSS
Percentile
82.5%
Cisco Discovery Protocol (CDP) is a proprietary layer-2 networking protocol that Cisco devices use to gather information about devices connected to the network. Armis Security found that CDP supported devices are vulnerable to heap overflow in Cisco IP Cameras (CVE-2020-3110), stack overflow in Cisco VoIP devices (CVE-2020-3111), a format string stack overflow vulnerability (CVE-2020-3118), stack overflow and arbitrary write (CVE-2020-3119), and a resource exhaustion denial-of-service vulnerability (CVE-2020-3120) in Cisco NX-OS switches and Cisco IOS XR Routers, among others. These vulnerabilities could allow an attacker on the local network to execute code or cause a denial of service.
CVE-2020-3110
Cisco’s Video Surveillance 8000 Series IP cameras with CDP enabled are vulnerable to a heap overflow in the parsing of DeviceID type-length-value (TLV). The CVSS score reflected below is in regards to this vulnerability.
CVE-2020-3111
Cisco Voice over Internet Protocol (VoIP) phones with CDP enabled are vulnerable to a stack overflow in the parsing of PortID type-length-value (TLV).
CVE-2020-3118
Cisco’s CDP subsystem of devices running, or based on, Cisco IOS XR Software are vulnerable to improper validation of string input from certain fields within a CDP message that could lead to a stack overflow.
CVE-2020-3119
Cisco’s CDP subsystem of devices running, or based on, Cisco NX-OS Software is vulnerable to a stack buffer overflow and arbitrary write in the parsing of Power over Ethernet (PoE) type-length-value (TLV).
CVE-2020-3120
Cisco’s CDP subsystem of devices running, or based on, Cisco NX-OS, IOS XR, and FXOS Software are vulnerable to a resource exhaustion denial-of-service condition.
CVE-2020-3110 and CVE-2020-3111, CVE-2020-3118, CVE-2020-3119
These vulnerabilities could allow a remote attacker on the local network to cause a denial of service by rebooting the affected device running CDP. A remote attacker could also execute code by sending a malicious unauthenticated CDP packet to the affected device.
**
CVE-2020-3120**
This vulnerability could allow a remote attacker on the local network to cause a denial of service by rebooting the affected device running CDP.
These vulnerabilities affect devices that have CDP enabled. It is important to note that for all affected devices, CDP is enabled by default. A complete list of the affected products can be found in the following Cisco advisories:
Apply an update
Please refer to Cisco’s advisories and support site for specific device updates.
Thanks to Ben Seri of Armis Security for reporting this vulnerability.
This document was written by Madison Oliver.
261385
Filter by status: All Affected Not Affected Unknown
Filter by content: __ Additional information available
__ Sort by: Status Alphabetical
Expand all
Updated: 2020-07-08 CVE-2020-3110 | Affected |
---|---|
CVE-2020-3111 | Affected CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Not Affected |
---|---|
CVE-2020-3111 | Not Affected CVE-2020-3118 |
Arista is not affected by the vulnerabilities listed here. Arista does not use Cisco products as a part of our own products which we offer for sale.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Not Affected |
---|---|
CVE-2020-3111 | Not Affected CVE-2020-3118 |
Belden devices do not implement Cisco Discovery Protocol and are therefore NOT AFFECTED by this vulnerability.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Not Affected |
---|---|
CVE-2020-3111 | Not Affected CVE-2020-3118 |
D-Link Branded products do not utilize the CDP protocol nor have deployed any software libraries specific to the protocols. D-Link Branded products are unaffected by CVE-2020-3110,CVE-2020-3111,CVE-2020-3118,CVE-2020-3119,CVE-2020-3120.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Not Affected |
---|---|
CVE-2020-3111 | Not Affected CVE-2020-3118 |
FreeBSD has never shipped with CDP in the base system. Users can install third-party software on FreeBSD which support the Cisco Discovery Protocol. None of the third-party applications we make available in our ports tree or distribute as binary packages contain the vulnerable Cisco code.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Not Affected |
---|---|
CVE-2020-3111 | Not Affected CVE-2020-3118 |
LANCOM Systems products are not vulnerable to these vulnerabilities.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Not Affected |
---|---|
CVE-2020-3111 | Not Affected CVE-2020-3118 |
We do not support Cisco Discovery Protocol on any of our devices and hence not affected by these issues.
Notified: 2020-02-05 Updated: 2020-07-08
Statement Date: February 05, 2020
CVE-2020-3110 | Not Affected |
---|---|
CVE-2020-3111 | Not Affected CVE-2020-3118 |
Pulse Secure Products are not vulnerable to these vulnerabilities.
Notified: 2020-07-02 Updated: 2020-07-08
Statement Date: July 02, 2020
CVE-2020-3110 | Not Affected |
---|---|
CVE-2020-3111 | Not Affected CVE-2020-3118 |
None of the Technicolor products embeds Cisco Discovery Protocol. This includes the products transferred in 2015 from acquisition of Cisco Connected Devices Division.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-04 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
Notified: 2020-02-05 Updated: 2020-07-08 CVE-2020-3110 | Unknown |
---|---|
CVE-2020-3111 | Unknown CVE-2020-3118 |
We have not received a statement from the vendor.
View all 217 vendors __View less vendors __
Group | Score | Vector |
---|---|---|
Base | 8.3 | AV:A/AC:L/Au:N/C:C/I:C/A:C |
Temporal | 8.3 | E:ND/RL:ND/RC:ND |
Environmental | 8.3 | CDP:ND/TD:ND/CR:ND/IR:ND/AR:ND |
CVE IDs: | CVE-2020-3110 CVE-2020-3111 CVE-2020-3118 CVE-2020-3119 CVE-2020-3120 |
---|---|
Date Public: | 2020-02-05 Date First Published: |
tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20200205-fxnxos-iosxr-cdp-dos
tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20200205-iosxr-cdp-rce
tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20200205-ipcameras-rce-dos
tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20200205-nxos-cdp-rce
tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20200205-voip-phones-rce-dos
www.cisco.com/en/US/technologies/tk652/tk701/technologies_white_paper0900aecd804cd46d.html
8.8 High
CVSS3
Attack Vector
ADJACENT_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:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
8.3 High
CVSS2
Access Vector
ADJACENT_NETWORK
Access Complexity
LOW
Authentication
NONE
Confidentiality Impact
COMPLETE
Integrity Impact
COMPLETE
Availability Impact
COMPLETE
AV:A/AC:L/Au:N/C:C/I:C/A:C
0.009 Low
EPSS
Percentile
82.5%