modified files

Author: ahouseholder

data/44/vu_988944/vu_988944.json

@@ -12,26 +12,26 @@
   "CAM_WidelyKnown": "0",
   "CERTAdvisory": "",
   "CVEIDs": "",
-  "CVSS_AccessComplexity": "",
-  "CVSS_AccessVector": "",
-  "CVSS_Authenication": "",
-  "CVSS_AvailabilityImpact": "",
-  "CVSS_BaseScore": "",
-  "CVSS_BaseVector": "",
-  "CVSS_CollateralDamagePotential": "",
-  "CVSS_ConfidentialityImpact": "",
-  "CVSS_EnvironmentalScore": "",
-  "CVSS_EnvironmentalVector": "",
-  "CVSS_Exploitability": "",
-  "CVSS_IntegrityImpact": "",
-  "CVSS_RemediationLevel": "",
-  "CVSS_ReportConfidence": "",
-  "CVSS_SecurityRequirementsAR": "",
-  "CVSS_SecurityRequirementsCR": "",
-  "CVSS_SecurityRequirementsIR": "",
-  "CVSS_TargetDistribution": "",
-  "CVSS_TemporalScore": "",
-  "CVSS_TemporalVector": "",
+  "CVSS_AccessComplexity": "--",
+  "CVSS_AccessVector": "--",
+  "CVSS_Authenication": "--",
+  "CVSS_AvailabilityImpact": "--",
+  "CVSS_BaseScore": 0,
+  "CVSS_BaseVector": "AV:--/AC:--/Au:--/C:--/I:--/A:--",
+  "CVSS_CollateralDamagePotential": "Not Defined (ND)",
+  "CVSS_ConfidentialityImpact": "--",
+  "CVSS_EnvironmentalScore": 0,
+  "CVSS_EnvironmentalVector": "CDP:Not Defined (ND)/TD:Not Defined (ND)/CR:Not Defined (ND)/IR:Not Defined (ND)/AR:Not Defined (ND)",
+  "CVSS_Exploitability": "Not Defined (ND)",
+  "CVSS_IntegrityImpact": "--",
+  "CVSS_RemediationLevel": "Not Defined (ND)",
+  "CVSS_ReportConfidence": "Not Defined (ND)",
+  "CVSS_SecurityRequirementsAR": "Not Defined (ND)",
+  "CVSS_SecurityRequirementsCR": "Not Defined (ND)",
+  "CVSS_SecurityRequirementsIR": "Not Defined (ND)",
+  "CVSS_TargetDistribution": "Not Defined (ND)",
+  "CVSS_TemporalScore": 0,
+  "CVSS_TemporalVector": "E:Not Defined (ND)/RL:Not Defined (ND)/RC:Not Defined (ND)",
   "DateCreated": "2002-01-17T13:47:42-05:00",
   "DateFirstPublished": "",
   "DateLastUpdated": "2002-01-17T13:48:00-05:00",

data/55/vu_988955/vu_988955.json

@@ -12,26 +12,26 @@
   "CAM_WidelyKnown": "0",
   "CERTAdvisory": "",
   "CVEIDs": "",
-  "CVSS_AccessComplexity": "",
-  "CVSS_AccessVector": "",
-  "CVSS_Authenication": "",
-  "CVSS_AvailabilityImpact": "",
-  "CVSS_BaseScore": "",
-  "CVSS_BaseVector": "",
-  "CVSS_CollateralDamagePotential": "",
-  "CVSS_ConfidentialityImpact": "",
-  "CVSS_EnvironmentalScore": "",
-  "CVSS_EnvironmentalVector": "",
-  "CVSS_Exploitability": "",
-  "CVSS_IntegrityImpact": "",
-  "CVSS_RemediationLevel": "",
-  "CVSS_ReportConfidence": "",
-  "CVSS_SecurityRequirementsAR": "",
-  "CVSS_SecurityRequirementsCR": "",
-  "CVSS_SecurityRequirementsIR": "",
-  "CVSS_TargetDistribution": "",
-  "CVSS_TemporalScore": "",
-  "CVSS_TemporalVector": "",
+  "CVSS_AccessComplexity": "--",
+  "CVSS_AccessVector": "--",
+  "CVSS_Authenication": "--",
+  "CVSS_AvailabilityImpact": "--",
+  "CVSS_BaseScore": 0,
+  "CVSS_BaseVector": "AV:--/AC:--/Au:--/C:--/I:--/A:--",
+  "CVSS_CollateralDamagePotential": "Not Defined (ND)",
+  "CVSS_ConfidentialityImpact": "--",
+  "CVSS_EnvironmentalScore": 0,
+  "CVSS_EnvironmentalVector": "CDP:Not Defined (ND)/TD:Not Defined (ND)/CR:Not Defined (ND)/IR:Not Defined (ND)/AR:Not Defined (ND)",
+  "CVSS_Exploitability": "Not Defined (ND)",
+  "CVSS_IntegrityImpact": "--",
+  "CVSS_RemediationLevel": "Not Defined (ND)",
+  "CVSS_ReportConfidence": "Not Defined (ND)",
+  "CVSS_SecurityRequirementsAR": "Not Defined (ND)",
+  "CVSS_SecurityRequirementsCR": "Not Defined (ND)",
+  "CVSS_SecurityRequirementsIR": "Not Defined (ND)",
+  "CVSS_TargetDistribution": "Not Defined (ND)",
+  "CVSS_TemporalScore": 0,
+  "CVSS_TemporalVector": "E:Not Defined (ND)/RL:Not Defined (ND)/RC:Not Defined (ND)",
   "DateCreated": "2001-08-30T15:38:10-04:00",
   "DateFirstPublished": "",
   "DateLastUpdated": "2001-09-06T12:05:00-04:00",

data/77/vu_647177/vu_647177.json

@@ -34,7 +34,7 @@
   "CVSS_TemporalVector": "E:ND/RL:ND/RC:ND",
   "DateCreated": "2019-12-10T12:57:54-05:00",
   "DateFirstPublished": "2020-05-18T13:59:42-04:00",
-  "DateLastUpdated": "2020-05-18T14:16:00-04:00",
+  "DateLastUpdated": "2020-05-26T09:49:00-04:00",
   "DatePublic": "2020-04-14T00:00:00",
   "Description": "Bluetooth is a short-range wireless technology based off of a core specification that defines six different core configurations, including the Bluetooth Basic Rate / Enhanced Data Rate (BR/EDR) Core Configurations. Bluetooth BR/EDR is used for low-power short-range communications. To establish an encrypted connection, two Bluetooth devices must pair with each other using a link key. It is possible for an unauthenticated, adjacent attacker to spoof the address of a previously paired remote device to successfully complete the authentication procedure with some paired/bonded devices without knowing the link key. The Bluetooth Impersonation Attack (BIAS) can be performed in two different ways, depending on which Secure Simple Pairing method (either Legacy Secure Connections or Secure Connections) was previously used to establish a connection between two devices. If the pairing procedure was completed using the Secure Connections method, the attacker could claim to be the previously paired remote device that no longer supports secure connections, thereby downgrading the authentication security. This would allow the attacker to proceed with the BIAS method against the legacy authentication unless the device they are attacking is in Secure Connections only mode. If the attacker can either downgrade authentication or is attacking a device that does not support Secure Connections, they can perform the attack using a similar method by initiating a master-slave role switch to place itself into the master role and become the authentication initiator. If successful, they complete the authentication with the remote device. If the remote device does not then mutually authenticate with the attacker in the master role, it will result in the authentication-complete notification on both devices, even though the attacker does not possess the link key. The BIAS method is able to be performed for the following reasons: Bluetooth secure connection establishment is not encrypted and the selection of secure connections pairing method is not enforced for an already established pairing, Legacy Secure Connections secure connection establishment does not require mutual authentication, a Bluetooth device can perform a role switch any time after baseband paging, and devices who paired using Secure Connections can use Legacy Secure Connections during secure connection establishment.",
   "ID": "VU#647177",
@@ -56,7 +56,7 @@
     "https://www.bluetooth.com/learn-about-bluetooth/bluetooth-technology/bluetooth-security/reporting-security/"
   ],
   "Resolution": "Bluetooth host and controller suppliers should refer to the Bluetooth SIG's statement for guidance on updating their products. Downstream vendors should refer to their suppliers for updates.",
-  "Revision": 30,
+  "Revision": 31,
   "SystemsAffectedPreamble": "",
   "ThanksAndCredit": "Thanks to Daniele Antonioli of Singapore University of Technology and Design, Nils Ole Tippenhauer of CISPA Helmholtz Center for Information Security, and Kasper Rasmussen of the University of Oxford for reporting this vulnerability.",
   "Title": "Bluetooth devices supporting BR/EDR are vulnerable to impersonation attacks",

data/95/vu_534195/vu_534195.json

@@ -34,7 +34,7 @@
   "CVSS_TemporalVector": "E:ND/RL:ND/RC:ND",
   "DateCreated": "2020-02-03T13:14:04-05:00",
   "DateFirstPublished": "2020-05-18T14:11:49-04:00",
-  "DateLastUpdated": "2020-05-18T14:12:00-04:00",
+  "DateLastUpdated": "2020-05-26T09:40:00-04:00",
   "DatePublic": "2020-05-18T00:00:00",
   "Description": "Bluetooth is a short-range wireless technology based off of a core specification that defines six different core configurations, including the Bluetooth Low Energy (BLE) Core Configuration. Like Bluetooth Classic (BR/ER), BLE is used for low-power short-range communications, but has significantly lower power consumption, making it ideal for Internet of Things (IoT) and other resource restricted devices. For two devices to communicate over BLE, they need to establish a connection by pairing via the (Low Energy) Secure Connections (SC or LESC) or Secure Simple Pairing (SSP) methods. The pairing process includes feature information exchange between devices on what they support, public key exchange, and authentication of the public keys using an Association Model. Two of the possible Association Models, Numeric Comparison (NC) and Passkey Entry (PE), are impacted by this attack. An adjacent, unauthenticated attacker can intercept the credentials shared during the pairing process and force each victim device into a different Association Model. To do this, the attacker must negotiate an NC procedure with one device and a PE procedure with the other, and the user must erroneously enter the NC value as the public key value and accept pairing on the NC device. This scenario applies to both BLE Secure Connections pairing and BR/EDR Secure Simple Pairing. However, only a device operating as a keyboard for the purposes of pairing may be used to enter the passkey in the BR/EDR Secure Simple Pairing scenario. The attacker would be able to initiate any Bluetooth operation on either attacked device that is exposed by the enabled Bluetooth profiles. For this attack to be successful, an attacking device must be within wireless range of two vulnerable Bluetooth devices that are establishing either an LE or a BR/EDR encrypted connection without existing shared credentials (long term key or link key). At least one device must permit entry of a passkey, and the other must support a display capable of representing six decimal digits. This attack is possible because the Association Models NC and PE use the same form of check value, the model used is not indicated to the user (making it extremely difficult to notice the change), and the devices are not authenticating which Association Model is used by the peer device.",
   "ID": "VU#534195",
@@ -52,7 +52,7 @@
     "https://www.bluetooth.com/learn-about-bluetooth/bluetooth-technology/bluetooth-security/reporting-security/"
   ],
   "Resolution": "Bluetooth host and controller suppliers should refer to the Bluetooth SIG's statement for guidance on updating their products. Downstream vendors should refer to their suppliers for updates.",
-  "Revision": 23,
+  "Revision": 24,
   "SystemsAffectedPreamble": "",
   "ThanksAndCredit": "Thanks to Ludwig Peuckert and Maximilian von Tschirschnitz for reporting this vulnerability.",
   "Title": "Bluetooth devices supporting LE and specific BR/EDR implementations are vulnerable to method confusion attacks",