Vulnerability-Lookup

CNVD-2018-00317

Vulnerability from cnvd - Published: 2018-01-05

Title

Vaultek Gun Safe VT20i信息泄露漏洞

Description

Vaultek Gun Safe VT20i（又名BlueSteal）是一款支持指纹识别的枪支保险箱产品。 Vaultek Gun Safe VT20i中存在信息泄露漏洞。远程攻击者可利用该漏洞打开该产品线中的任意保险箱。

Severity

高

Formal description

厂商尚未提供漏洞修复方案，请关注厂商主页及时更新： https://vaulteksafe.com/

Reference

https://www.twosixlabs.com/bluesteal-popping-gatt-safes/

Impacted products

Name
Vaultek Safe VT20i

Show details on source website

JSON

To clipboard

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2017-17435"
    }
  },
  "description": "Vaultek Gun Safe VT20i\uff08\u53c8\u540dBlueSteal\uff09\u662f\u4e00\u6b3e\u652f\u6301\u6307\u7eb9\u8bc6\u522b\u7684\u67aa\u652f\u4fdd\u9669\u7bb1\u4ea7\u54c1\u3002\r\n\r\nVaultek Gun Safe VT20i\u4e2d\u5b58\u5728\u4fe1\u606f\u6cc4\u9732\u6f0f\u6d1e\u3002\u8fdc\u7a0b\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u6253\u5f00\u8be5\u4ea7\u54c1\u7ebf\u4e2d\u7684\u4efb\u610f\u4fdd\u9669\u7bb1\u3002",
  "discovererName": "unknown",
  "formalWay": "\u5382\u5546\u5c1a\u672a\u63d0\u4f9b\u6f0f\u6d1e\u4fee\u590d\u65b9\u6848\uff0c\u8bf7\u5173\u6ce8\u5382\u5546\u4e3b\u9875\u53ca\u65f6\u66f4\u65b0\uff1a\r\nhttps://vaulteksafe.com/",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2018-00317",
  "openTime": "2018-01-05",
  "products": {
    "product": "Vaultek Safe VT20i"
  },
  "referenceLink": "https://www.twosixlabs.com/bluesteal-popping-gatt-safes/",
  "serverity": "\u9ad8",
  "submitTime": "2017-12-08",
  "title": "Vaultek Gun Safe VT20i\u4fe1\u606f\u6cc4\u9732\u6f0f\u6d1e"
}

CVE-2017-17435 (GCVE-0-2017-17435)

Vulnerability from cvelistv5 – Published: 2017-12-07 00:00 – Updated: 2024-08-05 20:51

Summary

An issue was discovered in the software on Vaultek Gun Safe VT20i products, aka BlueSteal. An attacker can remotely unlock any safe in this product line without a valid PIN code. Even though the phone application requires it and there is a field to supply the PIN code in an authorization request, the safe does not check the PIN code, so an attacker can obtain authorization using any value. Once an attacker sees the Bluetooth Low Energy (BLE) advertisement for the safe, they need only to write a BLE characteristic to enable notifications, and send a crafted getAuthor packet that returns a temporary key, and an unlock packet including that temporary key. The safe then opens after the unlock packet is processed, with no verification of PIN or other credentials.

Severity ?

No CVSS data available.

CWE

Assigner

mitre

References

URL

Tags

	https://vaulteksafe.com/index.php/cve-2017-17435/	x_refsource_CONFIRM
	https://www.twosixlabs.com/bluesteal-popping-gatt…	x_refsource_MISC

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-05T20:51:31.399Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "tags": [
              "x_refsource_CONFIRM",
              "x_transferred"
            ],
            "url": "https://vaulteksafe.com/index.php/cve-2017-17435/"
          },
          {
            "tags": [
              "x_refsource_MISC",
              "x_transferred"
            ],
            "url": "https://www.twosixlabs.com/bluesteal-popping-gatt-safes/"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "n/a",
          "vendor": "n/a",
          "versions": [
            {
              "status": "affected",
              "version": "n/a"
            }
          ]
        }
      ],
      "datePublic": "2017-12-06T00:00:00",
      "descriptions": [
        {
          "lang": "en",
          "value": "An issue was discovered in the software on Vaultek Gun Safe VT20i products, aka BlueSteal. An attacker can remotely unlock any safe in this product line without a valid PIN code. Even though the phone application requires it and there is a field to supply the PIN code in an authorization request, the safe does not check the PIN code, so an attacker can obtain authorization using any value. Once an attacker sees the Bluetooth Low Energy (BLE) advertisement for the safe, they need only to write a BLE characteristic to enable notifications, and send a crafted getAuthor packet that returns a temporary key, and an unlock packet including that temporary key. The safe then opens after the unlock packet is processed, with no verification of PIN or other credentials."
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "description": "n/a",
              "lang": "en",
              "type": "text"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2017-12-12T13:57:01",
        "orgId": "8254265b-2729-46b6-b9e3-3dfca2d5bfca",
        "shortName": "mitre"
      },
      "references": [
        {
          "tags": [
            "x_refsource_CONFIRM"
          ],
          "url": "https://vaulteksafe.com/index.php/cve-2017-17435/"
        },
        {
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://www.twosixlabs.com/bluesteal-popping-gatt-safes/"
        }
      ],
      "x_legacyV4Record": {
        "CVE_data_meta": {
          "ASSIGNER": "cve@mitre.org",
          "ID": "CVE-2017-17435",
          "STATE": "PUBLIC"
        },
        "affects": {
          "vendor": {
            "vendor_data": [
              {
                "product": {
                  "product_data": [
                    {
                      "product_name": "n/a",
                      "version": {
                        "version_data": [
                          {
                            "version_value": "n/a"
                          }
                        ]
                      }
                    }
                  ]
                },
                "vendor_name": "n/a"
              }
            ]
          }
        },
        "data_format": "MITRE",
        "data_type": "CVE",
        "data_version": "4.0",
        "description": {
          "description_data": [
            {
              "lang": "eng",
              "value": "An issue was discovered in the software on Vaultek Gun Safe VT20i products, aka BlueSteal. An attacker can remotely unlock any safe in this product line without a valid PIN code. Even though the phone application requires it and there is a field to supply the PIN code in an authorization request, the safe does not check the PIN code, so an attacker can obtain authorization using any value. Once an attacker sees the Bluetooth Low Energy (BLE) advertisement for the safe, they need only to write a BLE characteristic to enable notifications, and send a crafted getAuthor packet that returns a temporary key, and an unlock packet including that temporary key. The safe then opens after the unlock packet is processed, with no verification of PIN or other credentials."
            }
          ]
        },
        "problemtype": {
          "problemtype_data": [
            {
              "description": [
                {
                  "lang": "eng",
                  "value": "n/a"
                }
              ]
            }
          ]
        },
        "references": {
          "reference_data": [
            {
              "name": "https://vaulteksafe.com/index.php/cve-2017-17435/",
              "refsource": "CONFIRM",
              "url": "https://vaulteksafe.com/index.php/cve-2017-17435/"
            },
            {
              "name": "https://www.twosixlabs.com/bluesteal-popping-gatt-safes/",
              "refsource": "MISC",
              "url": "https://www.twosixlabs.com/bluesteal-popping-gatt-safes/"
            }
          ]
        }
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "8254265b-2729-46b6-b9e3-3dfca2d5bfca",
    "assignerShortName": "mitre",
    "cveId": "CVE-2017-17435",
    "datePublished": "2017-12-07T00:00:00",
    "dateReserved": "2017-12-05T00:00:00",
    "dateUpdated": "2024-08-05T20:51:31.399Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1"
}

Sightings

Author	Source	Type	Date

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Detection rules are retrieved from Rulezet.

Action not permitted

CNVD-2018-00317

CVE-2017-17435 (GCVE-0-2017-17435)

Tags

Sightings

Nomenclature