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
5.8 Medium
CVSS2
Access Vector
ADJACENT_NETWORK
Access Complexity
LOW
Authentication
NONE
Confidentiality Impact
PARTIAL
Integrity Impact
PARTIAL
Availability Impact
PARTIAL
AV:A/AC:L/Au:N/C:P/I:P/A:P
0.001 Low
EPSS
Percentile
31.0%
Devices supporting the Bluetooth Core and Mesh Specifications are vulnerable to impersonation attacks and AuthValue disclosure that could allow an attacker to impersonate a legitimate device during pairing.
The Bluetooth Core Specification and Mesh Profile Specification are two specifications used to define the technical and policy requirements for devices that want to operate over Bluetooth connections. Researchers at the Agence nationale de la sécurité des systèmes d’information (ANSSI) have identified a number of vulnerabilities in each specification that allow impersonation attacks and AuthValue disclosures.
Devices supporting the Bluetooth Core Specification are affected by the following vulnerabilities:
The Passkey Entry protocol used in Secure Simple Pairing (SSP), Secure Connections (SC), and LE Secure Connections (LESC) of the Bluetooth Core Specification is vulnerable to an impersonation attack that enables an active attacker to impersonate the initiating device without any previous knowledge (CVE-2020-26558). An attacker acting as a man-in-the-middle (MITM) in the Passkey authentication procedure could use a crafted series of responses to determine each bit of the randomly generated Passkey selected by the pairing initiator in each round of the pairing procedure, and once identified, the attacker can use these Passkey bits during the same pairing session to successfully complete the authenticated pairing procedure with the responder. Devices supporting BR/EDR Secure Simple Pairing in Bluetooth Core Specifications 2.1 through 5.2, BR/EDR Secure Connections Pairing in Bluetooth Core Specifications 4.1 through 5.2 and LE Secure Connections Pairing in Bluetooth Core Specifications 4.2 through 5.2 are affected by this vulnerability.
The Bluetooth BR/EDR PIN Pairing procedure is vulnerable to an impersonation attack (CVE-2020-26555). An attacker could connect to a victim device by spoofing the Bluetooth Device Address (BD_ADDR) of the device, reflect the the encrypted nonce, and complete BR/EDR pin-code pairing with them without knowledge of the pin code. A successful attack requires the attacking device to be within wireless range of a vulnerable device supporting BR/EDR Legacy Pairing that is Connectable and Bondable. Devices supporting the Bluetooth Core Specification versions 1.0B through 5.2 are affected by this vulnerability.
Devices supporting Bluetooth Mesh Profile Specification, versions 1.0 and 1.0.1, are affected by the following vulnerabilities:
The Mesh Provisioning procedure could allow an attacker without knowledge of the AuthValue, spoofing a device being provisioned, to use crafted responses to appear to possess the AuthValue and to be issued a valid NetKey and potentially an AppKey (CVE-2020-26560). For this attack to be successful, an attacking device needs to be within wireless range of a Mesh Provisioner and either spoof the identity of a device being provisioned over the air or be directly provisioned onto a subnet controlled by the provisioner.
The Mesh Provisioning procedure could allow an attacker observing or taking part in the provisioning to brute force the AuthValue if it has a fixed value, or is selected predictably or with low entropy (CVE-2020-26557). Identifying the AuthValue generally requires a brute-force search against the provisioning random and provisioning confirmation produced by the Provisioner. This brute-force search, for a randomly selected AuthValue, must complete before the provisioning procedure times out, which can require significant resources. If the AuthValue is not selected randomly with each new provisioning attempt, then the brute-force search can occur offline and if successful, would permit an attacker to identify the AuthValue and authenticate to both the Provisioner and provisioned devices, permitting a MITM attack on a future provisioning attempts with the same AuthValue.
The authentication protocol is vulnerable if the AuthValue can be identified during the provisioning procedure, even if the AuthValue is selected randomly (CVE-2020-26556). If an attacker can identify the AuthValue used before the provisioning procedure times out, it is possible to complete the provisioning operation and obtain a NetKey. Similar to CVE-2020-26557, identifying the AuthValue generally requires a brute-force search against the provisioning random and provisioning confirmation produced by the Provisioner. This brute-force search for a randomly selected AuthValue, which can require significant resources, must complete before the provisioning procedure times out.
The Mesh Provisioning procedure could allow an attacker that was provisioned without access to the AuthValue to identify the AuthValue directly without brute-forcing its value (CVE-2020-26559). Even when a randomly generated AuthValue with a full 128-bits of entropy is used, an attacker acquiring the Provisioner’s public key, provisioning confirmation value, and provisioning random value, and providing its public key for use in the provisioning procedure, will be able to compute the AuthValue directly.
This vulnerability could allow an attacker to authenticate to the response victim device and act as a legitimate encrypted device. The attacker cannot pair with the initiating device using this method of attack, which prevents a fully transparent man-in-the-middle attack between the initiator and responder. For this attack to be successful, an attacking device needs to be within wireless range of two vulnerable Bluetooth devices that are initiating pairing or bonding for which a BR/EDR IO Capabilities exchange or LE IO Capability in the pairing request and response results in the selection of the Passkey pairing procedure.
This vulnerability could allow an attacker to complete pairing with a known link key, encrypt communications with the vulnerable device, and access any profiles permitted by a paired or bonded remote device supporting Legacy Pairing.
This vulnerability could allow an attacker to successfully authenticate without the AuthValue. Once authenticated, the attacker could perform any operation permitted to a node provisioned on the subnet until it is either denied access or a new subnet is formed without the attacking node present.
This vulnerability could allow an attacker to successfully brute force the AuthValue and authenticate to both the Provisioner and provisioned devices, permitting a MITM attack on a future provisioning attempt with the same AuthValue.
This vulnerability could allow an attacker to obtain a NetKey, which could be used to decrypt and authenticate up to the network layer, allowing the relay of messages, but no application data decryption.
This vulnerability could allow an attacker to compute the AuthValue and authenticate to the Provisioner and provisioned devices.
Bluetooth users should ensure that they have installed the latest recommended updates from device and operating system manufacturers.
In addition to the two vulnerabilities affecting the Bluetooth Core Specification, the researchers also identified a potential security vulnerability related to LE Legacy Pairing authentication in Bluetooth Core Specification versions 4.0 through 5.2. The researchers claim that an attacker can reflect the confirmation and random numbers of a peer device in LE legacy pairing to successfully complete legacy authentication phase 2 without knowledge of the temporary key (TK). Because the attacker does not acquire a TK, or valid short-term key (STK) during this attack, completing authentication phase 2 is not sufficient for an encrypted link to be established. While the Bluetooth SIG does not consider this to be a method which can provide unauthorized access to a device, they still recommend that LE implementations requiring pairing and encryption use LE Secure Connections. The Bluetooth SIG also recommends that, where possible, implementations enable and enforce Secure Connections Only Mode, ensuring that LE legacy pairing cannot be used.
The Bluetooth SIG additionally makes the following recommendations for each vulnerability:
For the attack to succeed the pairing device needs to accept the same public key that it provided to the remote peer as the remote peer’s public key. The Bluetooth SIG recommends that potentially vulnerable implementations restrict the public keys accepted from a remote peer device to disallow a remote peer to present the same public key chosen by the local device, and the pairing procedure should be terminated with a failure status if this occurs.
The Bluetooth SIG recommends that potentially vulnerable devices not initiate or accept connections from remote devices claiming the same BD_ADDR as the local device. They also continue to recommend that devices use Secure Simple Pairing or BR/EDR Secure Connections to avoid known vulnerabilities with legacy BR/EDR pairing.
The Bluetooth SIG recommends that potentially vulnerable mesh provisioners restrict the authentication procedure and not accept provisioning both random and confirmation numbers from a remote peer that are the same as those selected by the local device.
The Bluetooth SIG recommends that mesh implementations enforce a randomly selected AuthValue using all of the available bits, where permitted by the implementation. A large entropy helps ensure that a brute-force of the AuthValue, even a static AuthValue, cannot normally be completed in a reasonable time.
The statement from the Bluetooth SIG notes: “AuthValues selected using a cryptographically secure random or pseudorandom number generator and having the maximum permitted entropy (128-bits) will be most difficult to brute-force. AuthValues with reduced entropy or generated in a predictable manner will not grant the same level of protection against this vulnerability. Selecting a new AuthValue with each provisioning attempt can also make it more difficult to launch a brute-force attack by requiring the attacker to restart the search with each provisioning attempt.”
The Bluetooth SIG recommends that potentially vulnerable mesh provisioners use an out-of-band mechanism to exchange the public keys.
Thanks to researchers at the Agence nationale de la sécurité des systèmes d’information (ANSSI) for reporting these vulnerabilities.
This document was written by Madison Oliver.
799380
Filter by status: All Affected Not Affected Unknown
Filter by content: __ Additional information available
__ Sort by: Status Alphabetical
Expand all
Notified: 2020-12-03 Updated: 2021-05-24
Statement Date: February 22, 2021
CVE-2020-26555 | Affected |
---|---|
Vendor Statement: | |
Android has assessed this issue as High severity for Android OS and will be issuing a patch for this vulnerability in an upcoming Android security bulletin. | |
CVE- 2020-26556 | Not Affected Vendor Statement: |
Android does not support Bluetooth Mesh so is not vulnerable. | |
CVE-2020-26557 | Not Affected Vendor Statement: |
Android does not support Bluetooth Mesh so is not vulnerable. | |
CVE-2020-26558 | Affected Vendor Statement: |
Android has reviewed this report and assessed this vulnerability as having impact on Android OS. We will be issuing a patch for this vulnerability in an upcoming Android security bulletin. | |
CVE-2020-26559 | Not Affected Vendor Statement: |
Android does not support Bluetooth Mesh so is not vulnerable. | |
CVE-2020-26560 | Not Affected Vendor Statement: |
Android does not support Bluetooth Mesh so is not vulnerable. | |
VU#799380.5 | Affected Vendor Statement: |
Our assessment of this report is that it is of negligible security impact on Android. |
Notified: 2020-12-03 Updated: 2021-05-24
Statement Date: April 26, 2021
CVE-2020-26555 | Affected |
---|---|
CVE- 2020-26556 | Not Affected CVE-2020-26557 |
Cisco is tracking these vulnerabilities via incident PSIRT-0503777710.
Cisco has investigated the impact of the aforementioned Bluetooth Specification vulnerabilities and is currently waiting for all the individual product development teams to provide Software fixes to address them.
Notified: 2020-12-03 Updated: 2021-05-26
Statement Date: May 25, 2021
CVE-2020-26555 | Not Affected |
---|---|
CVE- 2020-26556 | Not Affected CVE-2020-26557 |
Fixed in NCOS 7.21.40 | |
CVE-2020-26559 | Not Affected CVE-2020-26560 |
Fixed in NCOS 7.21.20 |
Cradlepoint’s MC20BT, Bluetooth Low Energy 5.1 Module, was released January 2021 and is compatible with E3000 and E300 Enterprise Branch routers.
The MC20BT is vulnerable to CVE-2020-26558 (patched in NCOS version 7.21.40) and VU#799380.5 (patched in NCOS version 7.21.20)
If you are using the MC20BT with an Enterprise series router, Cradlepoint recommends upgrade to 7.21.40 or higher. For more information regarding upgrading your Cradlepoint device, visit our knowledgebase.
https://customer.cradlepoint.com/s/article/Best-Practice-Stairstepping-NCOS-Upgrades
Notified: 2020-12-03 Updated: 2021-12-09
Statement Date: December 09, 2021
CVE-2020-26555 | Affected |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2021-06-14 Updated: 2021-08-05
Statement Date: August 05, 2021
CVE-2020-26555 | Affected |
---|---|
CVE- 2020-26556 | Not Affected CVE-2020-26557 |
Fujitsu is aware of the security vulnerabilities in Bluetooth devices under VU#799380.
Fujitsu products are not affected by INTEL-SA-00517, but are affected by INTEL-SA-00520, i.e. CVE-2020-26555 and CVE-2020-26558.
Fujitsu has already provided Software updates for Intel® Wi-Fi 6 AX201, Intel® Wireless-AC 9560, Intel® Dual Band Wireless-AC 8265 and Intel® Dual Band Wireless-AC 8260 components employed in Fujitsu mobile products and Fujitsu INTELLIEDGE.
The Fujitsu PSIRT has updated the state for Fujitsu PSS-IS-2021-060800 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-12-03 Updated: 2021-05-24
Statement Date: March 18, 2021
CVE-2020-26555 | Affected |
---|---|
CVE- 2020-26556 | Not Affected CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-26
Statement Date: May 24, 2021
CVE-2020-26555 | Affected |
---|---|
CVE- 2020-26556 | Not Affected CVE-2020-26557 |
Microchip is aware of multiple Bluetooth Core specification vulnerabilities. We have determined that some CVEs affect some of our Bluetooth products. For details on impacted products and resolution plans, visit below URL
Notified: 2020-12-03 Updated: 2021-05-24
Statement Date: May 24, 2021
CVE-2020-26555 | Affected |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-26
Statement Date: May 25, 2021
CVE-2020-26555 | Affected |
---|---|
CVE- 2020-26556 | Affected CVE-2020-26557 |
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 the researchers at the Agence Nationale de la Sécurité des Systèmes d’information (ANSSI) for reporting these vulnerabilities, as well as the efforts of CERT/CC for coordinating the response.
Notified: 2020-12-03 Updated: 2021-06-23
Statement Date: June 23, 2021
CVE-2020-26555 | Not Affected |
---|---|
CVE- 2020-26556 | Not Affected CVE-2020-26557 |
Bluetooth is not a supported feature or capability in any A10 Networks, Inc products.
Notified: 2020-12-03 Updated: 2021-05-24
Statement Date: January 21, 2021
CVE-2020-26555 | Not Affected |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We are not currently using Bluetooth on any of our products.
Notified: 2020-12-03 Updated: 2021-05-24
Statement Date: February 16, 2021
CVE-2020-26555 | Not Affected |
---|---|
CVE- 2020-26556 | Not Affected CVE-2020-26557 |
No ADTRAN products have Bluetooth enabled at this time.
Notified: 2020-12-03 Updated: 2021-05-24
Statement Date: February 16, 2021
CVE-2020-26555 | Not Affected |
---|---|
CVE- 2020-26556 | Not Affected CVE-2020-26557 |
Arista products do not use bluetooth and are therefore not affected.
Notified: 2020-12-03 Updated: 2021-05-24
Statement Date: February 12, 2021
CVE-2020-26555 | Not Affected |
---|---|
CVE- 2020-26556 | Not Affected CVE-2020-26557 |
AVM doesn’t produce Bluetooth products. We did 18 years ago, but these devices reached their end of life status very long time ago.
Notified: 2020-12-03 Updated: 2021-05-24
Statement Date: January 19, 2021
CVE-2020-26555 | Not Affected |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24
Statement Date: February 17, 2021
CVE-2020-26555 | Not Affected |
---|---|
CVE- 2020-26556 | Not Affected CVE-2020-26557 |
Belden devices do not support Bluetooth and are not affected by these vulnerabilities.
Notified: 2020-12-03 Updated: 2021-05-24
Statement Date: March 19, 2021
CVE-2020-26555 | Not Affected |
---|---|
CVE- 2020-26556 | Not Affected CVE-2020-26557 |
No Brocade Fibre Channel Products from Broadcom products are affected by this vulnerability.
Notified: 2020-12-03 Updated: 2021-05-24
Statement Date: April 11, 2021
CVE-2020-26555 | Not Affected |
---|---|
Vendor Statement: | |
we dont have bluetooth stack in our products | |
CVE- 2020-26556 | Unknown CVE-2020-26557 |
we dont have bluetooth stack in our products | |
CVE-2020-26559 | Unknown CVE-2020-26560 |
we dont have bluetooth stack in our products |
we dont have bluetooth stack in our products
Notified: 2020-12-03 Updated: 2021-05-24
Statement Date: March 21, 2021
CVE-2020-26555 | Not Affected |
---|---|
CVE- 2020-26556 | Not Affected CVE-2020-26557 |
Check Point doesn’t use Bluetooth in its appliances.
Notified: 2020-12-03 Updated: 2021-05-24
Statement Date: December 07, 2020
CVE-2020-26555 | Not Affected |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-09-01
Statement Date: September 01, 2021
CVE-2020-26555 | Not Affected |
---|---|
CVE- 2020-26556 | Not Affected CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24
Statement Date: February 16, 2021
CVE-2020-26555 | Not Affected |
---|---|
CVE- 2020-26556 | Not Affected CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24
Statement Date: December 04, 2020
CVE-2020-26555 | Not Affected |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We do not build or install any component of the Bluetooth drivers in the BIG-IP, so those vulnerabilities do not affect F5 BIG-IP products.
Notified: 2020-12-03 Updated: 2021-05-24
Statement Date: December 14, 2020
CVE-2020-26555 | Not Affected |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24
Statement Date: March 25, 2021
CVE-2020-26555 | Not Affected |
---|---|
CVE- 2020-26556 | Not Affected CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24
Statement Date: February 16, 2021
CVE-2020-26555 | Not Affected |
---|---|
Vendor Statement: | |
HCC does not use Bluetooth stack so not affected. | |
CVE- 2020-26556 | Not Affected CVE-2020-26557 |
HCC does not use Bluetooth stack so not affected. | |
CVE-2020-26559 | Not Affected CVE-2020-26560 |
HCC does not use Bluetooth stack so not affected. |
HCC does not use Bluetooth stack so not affected.
Notified: 2020-12-03 Updated: 2021-05-24
Statement Date: March 18, 2021
CVE-2020-26555 | Not Affected |
---|---|
CVE- 2020-26556 | Not Affected CVE-2020-26557 |
illumos, nor its distributions, have a native bluetooth stack. If a distribution has a bluetooth stack, it originated from another open-source package.
Notified: 2020-12-03 Updated: 2021-05-24
Statement Date: April 09, 2021
CVE-2020-26555 | Not Affected |
---|---|
CVE- 2020-26556 | Not Affected CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24
Statement Date: March 18, 2021
CVE-2020-26555 | Not Affected |
---|---|
Vendor Statement: | |
Upstream illumos does not have a Bluetooth stack, neither does SmartOS. | |
CVE- 2020-26556 | Not Affected Vendor Statement: |
Upstream illumos does not have a Bluetooth stack, neither does SmartOS. | |
CVE-2020-26557 | Not Affected Vendor Statement: |
Upstream illumos does not have a Bluetooth stack, neither does SmartOS. | |
CVE-2020-26558 | Not Affected Vendor Statement: |
Upstream illumos does not have a Bluetooth stack, neither does SmartOS. | |
CVE-2020-26559 | Not Affected Vendor Statement: |
Upstream illumos does not have a Bluetooth stack, neither does SmartOS. | |
CVE-2020-26560 | Not Affected Vendor Statement: |
Upstream illumos does not have a Bluetooth stack, neither does SmartOS. | |
VU#799380.5 | Not Affected Vendor Statement: |
Upstream illumos does not have a Bluetooth stack, neither does SmartOS. |
SmartOS is a distrubtion of illumos, and does not include a native or distribution-specific bluetooth stack.
Notified: 2020-12-03 Updated: 2021-05-24
Statement Date: May 20, 2021
CVE-2020-26555 | Not Affected |
---|---|
CVE- 2020-26556 | Not Affected CVE-2020-26557 |
See https://www.lancom-systems.com/service-support/instant-help/general-security-information/ for details.
Notified: 2020-12-03 Updated: 2021-05-24
Statement Date: February 17, 2021
CVE-2020-26555 | Not Affected |
---|---|
Vendor Statement: | |
lwIP does not have a bluetooth stack, so we’re not affected. | |
CVE- 2020-26556 | Not Affected CVE-2020-26557 |
lwIP does not have a bluetooth stack, so we’re not affected. | |
CVE-2020-26559 | Not Affected CVE-2020-26560 |
lwIP does not have a bluetooth stack, so we’re not affected. |
lwIP does not have a bluetooth stack, so we’re not affected.
Notified: 2020-12-03 Updated: 2021-05-24
Statement Date: May 17, 2021
CVE-2020-26555 | Not Affected |
---|---|
CVE- 2020-26556 | Not Affected CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2023-07-13
Statement Date: July 13, 2023
CVE-2020-26555 | Not Affected |
---|---|
CVE- 2020-26556 | Not Affected CVE-2020-26557 |
MikroTik Bluetooth implementation does not work in a peer-to-peer scenario, where pairing is involved. MikroTik devices work in Bluetooth Advertiser and Scanner topologies, where Bluetooth devices advertise/broadcast data over Bluetooth advertising channels, and MikroTik routers just scan the air to capture the Bluetooth payloads. Once again, there is no pairing involved. Pairing scenarios are scenarios where, for example, your phone connects to your headset, making a peer-to-peer connection between the two devices. In MikroTik’s case, we do not support pairing, so it does not affect us. MESH vulnerabilities also do not affect us, as MikroTik does not support this feature.
Notified: 2020-12-03 Updated: 2021-05-24
Statement Date: January 19, 2021
CVE-2020-26555 | Not Affected |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
Not concerned with Bluetooth.
Notified: 2020-12-03 Updated: 2021-06-24
Statement Date: June 24, 2021
CVE-2020-26555 | Not Affected |
---|---|
CVE- 2020-26556 | Not Affected CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24
Statement Date: April 25, 2021
CVE-2020-26555 | Not Affected |
---|---|
CVE- 2020-26556 | Not Affected CVE-2020-26557 |
Not affected. |
Not affected.
Notified: 2020-12-03 Updated: 2021-06-03
Statement Date: June 03, 2021
CVE-2020-26555 | Not Affected |
---|---|
CVE- 2020-26556 | Not Affected CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24
Statement Date: December 14, 2020
CVE-2020-26555 | Not Affected |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24
Statement Date: April 20, 2021
CVE-2020-26555 | Not Affected |
---|---|
CVE- 2020-26556 | Not Affected CVE-2020-26557 |
Zyxel products are NOT affected because they don’t support the authentication pairing functions, the mesh profile, or do not support Bluetooth at all.
Notified: 2020-12-11 Updated: 2021-05-24
Statement Date: May 21, 2021
CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-10-27 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2021-02-17 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
Notified: 2020-12-03 Updated: 2021-05-24 CVE-2020-26555 | Unknown |
---|---|
CVE- 2020-26556 | Unknown CVE-2020-26557 |
We have not received a statement from the vendor.
View all 249 vendors __View less vendors __
CVE IDs: | CVE-2020-26555 [CVE- 2020-26556 ](<http://web.nvd.nist.gov/vuln/detail/CVE- 2020-26556>) CVE-2020-26557 CVE-2020-26558 CVE-2020-26559 CVE-2020-26560 |
---|---|
API URL: | VINCE JSON |
Date Public: | 2021-05-24 Date First Published: |
www.bluetooth.com/learn-about-bluetooth/key-attributes/bluetooth-security/authvalue-leak/
www.bluetooth.com/learn-about-bluetooth/key-attributes/bluetooth-security/impersonation-mesh/
www.bluetooth.com/learn-about-bluetooth/key-attributes/bluetooth-security/impersonation-pin-pairing/
www.bluetooth.com/learn-about-bluetooth/key-attributes/bluetooth-security/legacy-pairing/
www.bluetooth.com/learn-about-bluetooth/key-attributes/bluetooth-security/malleable/
www.bluetooth.com/learn-about-bluetooth/key-attributes/bluetooth-security/passkey-entry/
www.bluetooth.com/learn-about-bluetooth/key-attributes/bluetooth-security/predicatable-authvalue/
www.bluetooth.com/learn-about-bluetooth/key-attributes/bluetooth-security/reporting-security/
www.bluetooth.com/specifications/specs/core-specification/
www.bluetooth.com/specifications/specs/mesh-profile-1-0-1/
www.ieee-security.org/TC/SP2021/SPW2021/WOOT21/
www.novelbits.io/bluetooth-mesh-tutorial-part-3/
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
5.8 Medium
CVSS2
Access Vector
ADJACENT_NETWORK
Access Complexity
LOW
Authentication
NONE
Confidentiality Impact
PARTIAL
Integrity Impact
PARTIAL
Availability Impact
PARTIAL
AV:A/AC:L/Au:N/C:P/I:P/A:P
0.001 Low
EPSS
Percentile
31.0%